question about A1200 kernel source

[xqterry]

A1200 kernel source on opensource motorola is marked 42P clean. I download, extract it, but it seems 2.4.17(A1200 is 2.4.20) and in the setup.sh file:

echo "usage: ./setup.sh [PRODUCT=E680|PRODUCT=E680I|PRODUCT=A780|?]"

Is this source really for A1200? or from 44P motorola upgrade the source to revision 2.4.20 ?

* I think it's possible to replace kernel image with a hacked .sbf file, I've tested to add busybox into /bin of rootfs then replace 44.smg and modified 16bit checksum, RSD lite flashed my phone successfully with the hacked .sbf file.

thanks.

[rpconnect]

A1200 kernel source on opensource motorola is marked 42P clean. I download, extract it, but it seems 2.4.17(A1200 is 2.4.20) and in the setup.sh file:

echo "usage: ./setup.sh [PRODUCT=E680|PRODUCT=E680I|PRODUCT=A780|?]"

Is this source really for A1200? or from 44P motorola upgrade the source to revision 2.4.20 ?

it was the same as for the e680 kernel when it was made available, it was labeled as 2.4.17 but somwhere within a configuration it was actually using 2.4.20.

* I think it's possible to replace kernel image with a hacked .sbf file, I've tested to add busybox into /bin of rootfs then replace 44.smg and modified 16bit checksum, RSD lite flashed my phone successfully with the hacked .sbf file.

that's great news! have you or anyone tried to use the flash-kit on the a1200? for little changes like including stuff in /bin, /lib, or /dev i found flashkit to be great (at least on an e680, don't have an a1200 yet but its coming soon...)

[xqterry]

it was the same as for the e680 kernel when it was made available, it was labeled as 2.4.17 but somwhere within a configuration it was actually using 2.4.20.

run setup.sh as E680 then build it, is it OK? I haven't built it, because I am not sure if I get the correct source.

thanks.

that's great news! have you or anyone tried to use the flash-kit on the a1200? for little changes like including stuff in /bin, /lib, or /dev i found flashkit to be great (at least on an e680, don't have an a1200 yet but its coming soon...)

I checked the flashkit file, it is different between 680 and 1200.

@ A1200 kernel version is 2.4.20_mvlcee31-mainstone_pxa27, fwflash.o was compiled for 2.4.20_mvlcee30-mainstone. To use flashkit, we have to rebuild it.
@ /diska mount point does not exist on A1200
@ The content of /proc/mtd is different, kernel image is mtd7 on A1200 but mtd4 on 680. and rootfs is not listed in /proc/mtd.
@ smg file of A1200 firmware contains a motorola's header (<4k) before the content of the cramfs image, and I dumpped mtd7 with dd, it also contains motorola's header. If flashkit works on A1200, we should add the header to hacked cramfs image, or dd the cramfs image with correct offset.

I have not read source of flashkit yet, but obviously it needs to be modified for working on A1200.

[rpconnect]

@xqterry
Thanks for the info, my 1200 is not here yet, and i've never fully gotten into rebuilding the kernel sources available, but as i will be wanting to rebuild modules asap (e.g. for bluez) i suppose i should learn.

i'm waiting for openezx to come back up, as soon as i can i'm going to try to build the kernel sources for e680 and a1200 separately to see what happens...

on a side note, what happens with using "insmod -f" for loading "older" modules on the a1200? it appears that a similar thing is being tried for faking the gprs and that "insmod -f" will get the module to load (although there seems to be still some question as to weather or not its working correctly...)

[xqterry]

To rpconnect

I have tried insmod -f, but failed.

# insmod -f rwflash.o
Warning: kernel-module version mismatch
rwflash.o was compiled for kernel version 2.4.20_mvlcee30-mainstone
while this kernel is version 2.4.20_mvlcee31-mainstone_pxa27
rwflash.o: unresolved symbol __get_mtd_device

I also should learn more and more, that is why the life is funny I think. If moto opens everything, it maybe funny but should never more than now.

[rpconnect]

To xqterry:

thanks for trying, i guess we'll be learning together

i just downloaded the e680-a780 and a1200 kernel sources from opensource motorola and (hopefully) will try building both later today. with any luck i will soon be able to replicate the build that cyph did to get working bluez for the e680, then i can try to re-do it under the a1200 kernel (i really want bluez...)

[blackhawk]

@rpconnect
Talking about bluez, how about rfcomm socket support? KDE Bluetooth Team write a lot of bluez library helper to make bluez coding from qt more easy, for an example rfcommsocket class sub-classing qsocket!

RfcommSocket *s = new RfcommSocket();
s->connectToHost(addr, chan);
s->writeBlock("Hello", 5);
s->close();

I need working rfcomm socket support & bluetooth dongle too

[rpconnect]

@blackhawk
do you know if this is something that is supported in bluez 3.4?

i'm still trying to figure out how to build the a1200 kernel source so that something gets built in the bluetooth directory; if i can get something built then perhaps get the bluez kernel patch to work, or at least a subset of it. any suggestions for a module building newb?

[xqterry]

@rpconnect

how about kernel building? I did it with ezx-crosstool-0.5 but compile failed. Could you do it smoothly?

thanks

[rpconnect]

@xqterry
i was able to complete a build, but i'm not sure if it exactly the same kernel as the a1200.

I followed the directions from openezx for building the e680/a780 kernel. note that when you apply pnail's patch almost everything fails except the patch to the iwmmx code, but i think this may be all we need; after that i copied the only ezx-related config file i could find from arch/arm/def-configss/ezx-hainan to .config and went through the four make commands (oldconfig, dep, zImage and modules).

it is not clear from the config file that hainan is associated with the a1200, but i thought i'd give it a try.