I guess one parallel thread is going for the same problem and I can stick to that instead. Thanks for ur reply anil.
On Sep 10, 1:39 pm, "Anil Sasidharan" <[EMAIL PROTECTED]> wrote: > Hi, > > I was able to bring up Android (both m5 and sdk-v09) on OMAP3430 > platform. One of the important points is to turn of the TLS_REGISTER in > arch/arm/mm/Kconfig while building the kernel. Android's bionic libc does > not support TLS register yet. This could be the reason why "init" is > failing. > > Warm Regards, > Anil > > > > On Wed, Sep 10, 2008 at 11:07 AM, Neo <[EMAIL PROTECTED]> wrote: > > > Hi All, > > I have ported android on OMAP2430 successfully with m3 filesystem > > and it works fine. I am getting the problem when I am porting the same > > kernel (2.6.26) for omap3430. The last error I am getting is Kernel > > panic, > > "Kernel panic - not syncing: Attempted to kill init! " > > Also I got one warning regarding init console. > > "Warning: unable to open an initial console" > > > I tried to find out what exactly it mean but could not find anything > > regarding this. > > > To let u know, I am using the same kernel (with android changes) used > > for OMAP2430 for OMAP3430 ( by configuring it for OMAP3430). > > > thanks- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to android-internals@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-internals?hl=en -~----------~----~----~----~------~----~------~--~---
