Porting Andoid on A1200 MING

[bmoqimi]

copy and rename the config file to .config to the root of the kernel tree, and type make ARCH=arm oldconfig
This is why you get this message.
You have that Kernel hacking - linux-2.6 - OpenEZX page that is helpful.
Or you need to do a "make clean" or better "make mrproper"

oh thanks for the quick response
but which config file you mean I should rename ?

[sabrod]

but which config file you mean I should rename ?

Hehe. I don't know, i suppose you have that file... (def-config?? ezx-defconfig?? config ? kernel-config??? "show hidden files"? "find . -iname config") still nothing? "find kernel-dir/ -exec grep "CONFIG_PXA27x=y" '{}' \; -print" !!!
...nothing? I end up!
Ah: this, maybe... i don't get it! There is no need of a minimum of experience in kernel compiling before trying to port android to a new platform? Cool!

[bmoqimi]

Hehe. I don't know, i suppose you have that file... (def-config?? ezx-defconfig?? config ? kernel-config??? "show hidden files"? "find . -iname config") still nothing? "find kernel-dir/ -exec grep "CONFIG_PXA27x=y" '{}' \; -print" !!!
...nothing? I end up!
Ah: Let me google that for you i don't get it, there a need of

I never imagined somebody would answer me what i told every one !
I am so ashamed of your response !
I did the config with what you told and it says it is all written to .config file
I am going through the rest of the process making !

[sabrod]

Hehe, arf, it wasn't made to "impress" anyone... if you are ashamed, it's because at least you understood what make the 2 last find commands, and that's very good !
After all you could perfectly begin to learn kernel compilation with a patched ARM version... At least you'll not break your PC, but your phone

[bmoqimi]

changing manu things to .config did not respond well
and the new problem is that :

babak@ubuntu:~/making/linux-2.6.24$ make -f patches/Makefile.openezx
make: *** No rule to make target `zImage-a1200', needed by `all'.  Stop.

a bit confused !

[sabrod]

Hum, i would adapt from Kernel hacking - linux-2.6 - OpenEZX
I don't know, but at the time the android-ezx tuto was written, it guess the stuff was made like this:
Edit Makefile.openezx as android-ezx guy suggested:
PHONES = a1200
CROSS_COMPILE ?=<path and prefix- of the cross-compiler>
then

cd linux-kernel-tree
cp patches/defconfig-a1200 .config
make -f patches/Makefile.openezx

No rules error seems to be because Makefiles scripts can't find the "config"...??

[sabrod]

Kernel hacking - Archive (revision of feb, 200
Here is the old style of OpenEzx compilation...
Obviously , the last make command is :

make -f patches/Makefile.OpenEZX CROSS_COMPILE=<path to your toolchain>

[bmoqimi]

did you yourself did the porting by the way?
I am going to try what you said

[bmoqimi]

everything started working thanks to your help
and in the middle of making i got this :

  LD      .tmp_vmlinux1
kernel/built-in.o: In function `getnstimeofday':
utsname_sysctl.c:(.text+0x229f8): undefined reference to `__aeabi_uldivmod'
kernel/built-in.o: In function `do_gettimeofday':
utsname_sysctl.c:(.text+0x22aa4): undefined reference to `__aeabi_uldivmod'
utsname_sysctl.c:(.text+0x22ac4): undefined reference to `__aeabi_uldivmod'
kernel/built-in.o: In function `timekeeping_resume':
utsname_sysctl.c:(.text+0x22c68): undefined reference to `__aeabi_uldivmod'
utsname_sysctl.c:(.text+0x22c84): undefined reference to `__aeabi_uldivmod'
kernel/built-in.o:utsname_sysctl.c:(.text+0x23300): more undefined references to `__aeabi_uldivmod' follow
make[1]: *** [.tmp_vmlinux1] Error 1
make[1]: Leaving directory `/home/babak/making/linux-2.6.24'
make: *** [zImage-a1200] Error 2

going to search a bit more
merci beaucoup

[sabrod]

You are at the end of the compiling...
Its so sad...
What is your toolchain?? Maybe your system need to use another func to "getnstimeofday", i would grep (or find . -exec grep "__aeabi_uldivmod" to see if there is something to do, actually it would be cool if it was just a little option on a makefile, sorry, i reply blindly, i dunno more...)
Good luck...
No, i never tried this android test version, i'm willing to do this on .27 or .29 but i'm not really a coder... ( at least a linux driver one! ).