Hello, the sreenshot shows that you boot to address 0xc0000000. I use a SMDK6410 board booted your kernel to address 0xc0008000, that boots up to the android init process.
I had a quick lock to the kernel at git://www.kandroid.org/samsung-s3c6410-android.1.0. It is a 2.24 kernel with the android driver added. Somewhere I have seen a list of changes needed in the kernel need for the complete android system. Does your version contain all of the changes ? I´m not sure which is the best way run android on the s3c6410. Should one: A) Add the android drivers to the 2.24 Samsung kernel ( as in this source ) ? B) Add the samsung drivers from the samsung s3c6410 kernel to the android kernel. Location of some include file are changed and some function are different ( set_ktype_name .... ) C) Add the samsung drivers from the 2.29 kernel to the android kernel. D) Add the android drivers to the 2.29 kernel ? Can anybody tell something about the potential problems with the different options ? Best regards Carsten On 27 Mrz., 07:16, huymq85 <[email protected]> wrote: > hi all, > I have created a kernel image for Samsung s3c6410 using git : > > git clone git://www.kandroid.org/samsung-s3c6410-android.1.0 > > toolchain > :http://www.kandroid.org/~open/devtools/kandroid-1.1.2.1-20080530.glib... > > But when booting, i have a problem, this is the captrue: > > http://www.freeimagehosting.net/image.php?8a26c8fe25.jpg > > please tell me why? thanks you very much. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
