Hey Mohan, If you're actively working on this ... maybe you want to join the android-on-n8xx as well, in order to document your findings on that website and add your patches etc, for other people to find ?
Just let me know... ( http://code.google.com/p/android-on-n8xx/ ) Mohan Parthasarathy wrote: > Hi George, > > I fixed the alarm driver problem. At least, it looks like the > misc_register should be called in __init and > not in late_init. Interestingly, i get other errors which i did not > get before :-) runtime seems to get > EINVALs and coredumps. > > in my reading of this thread, i thought m5 filesystem had issues with > n810. Is that right ? Are you > suggesting to use both m5 filesystem and m5 kernel ? I tried this > early on and then reverted to > m3. In the pointer below, the versions are not mentioned. > > thanks > mohan > > > On Mon, Apr 21, 2008 at 10:12 AM, Georges Toth <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > Hi, > > Mohan Parthasarathy wrote: > > This is exactly the problem i am having since yesterday. I am > > debugging currently.. > > Also, i use m3 kernel and m3 filesystem and i see the same > entries in > > /proc/misc > > entries. Let me know if you find something or someone has clues.. > > > > -thx > > mohan > Use the m5 kernel instead. > If you don't see a binder entry in /proc/misc it for sure won't > work... > (there also has to be a node in /dev of course..) > Also checkout elinux.org <http://elinux.org> and > http://code.google.com/p/android-on-n8xx/ ... > > -- > regards, > > Georges Toth > > > > > > > -- regards, Georges Toth --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
