Hi Anil, After adding the following settings in init.rc , my system doesn't even boots up :(
Is there any specific place in init.rc where i should insert these settings ?? Or other than this shall I need to do anythng else..?? I am pasting the boot logs which i am getting :- OHZ: local_softirq_pending 20 NOHZ: local_softirq_pending 20 NOHZ: local_softirq_pending 20 NOHZ: local_softirq_pending 20 NOHZ: local_softirq_pending 20 NOHZ: local_softirq_pending 20 NOHZ: local_softirq_pending 20 binder: release proc 1056, transaction 5204, not freed NOHZ: local_softirq_pending 20 binder: release 1208:1217 transaction 7181 out, still active binder: release 1208:1218 transaction 7191 out, still active binder: 649:654 transaction failed 29189, size 20-4 binder: send failed reply for transaction 7191, target dead binder: 649:649 transaction failed 29189, size 13124-0 binder: send failed reply for transaction 7181, target dead binder: release proc 1223, transaction 7374, not freed binder: release proc 1981, transaction 17745, not freed binder: release proc 2127, transaction 19641, not freed binder: release 3903:3911 transaction 43260 out, still active binder: release 3903:3912 transaction 43288 out, still active binder: 649:649 transaction failed 29189, size 8-0 binder: send failed reply for transaction 43288, target dead binder: 649:655 transaction failed 29189, size 13124-0 binder: send failed reply for transaction 43260, target dead binder: release proc 4373, transaction 49585, not freed binder: release proc 4609, transaction 52803, not freed binder: release proc 5667, transaction 66971, not freed binder: release proc 6108, transaction 72815, not freed binder: release 6658:6667 transaction 80064 out, still active binder: release 6658:6668 transaction 80093 out, still active binder: 649:655 transaction failed 29189, size 8-0 binder: send failed reply for transaction 80093, target dead binder: 649:653 transaction failed 29189, size 13124-0 binder: send failed reply for transaction 80064, target dead binder: release proc 6820, transaction 82313, not freed binder: release proc 7729, transaction 94727, not freed binder: release 7846:7854 transaction 96125 out, still active binder: release 7846:7855 transaction 96135 out, still active binder: 649:1222 transaction failed 29189, size 20-4 binder: send failed reply for transaction 96135, target dead binder: 649:653 transaction failed 29189, size 13124-0 binder: send failed reply for transaction 96125, target dead binder: release 8128:8137 transaction 99905 out, still active binder: release 8128:8138 transaction 99919 out, still active binder: 649:649 transaction failed 29189, size 48-0 binder: 649:649 transaction failed 29189, size 4-0 binder: send failed reply for transaction 99919, target dead binder: 649:1222 transaction failed 29189, size 13124-0 binder: send failed reply for transaction 99905, target dead Thanks & Regards Nimit On Thu, Nov 27, 2008 at 7:47 PM, kapare <[EMAIL PROTECTED]>wrote: > > Hi Anil, > > You said that you have done the porting for 2.6.26, yes I'm > interested. > > Did you start with 2.6.22.18 from OMAP35x_SDK_0.9.5 then port to > 2.6.26 + android ? > > Can you guide me from the beginning? I mean what are the first steps > and where did you take that 2.6.26? > > Regards > > kap > > On Nov 27, 8:34 am, "Anil Sasidharan" <[EMAIL PROTECTED]> wrote: > > Hi Nimit, > > > > To enable networking do the following in the init.rc file > > > > setprop net.gprs.local-ip <board's-ip-address> > > setprop net.dns1 <primary-dns-server-ip> > > setprop net.dns2 <secondary-dns-server-ip> > > > > We've not tested Bluetooth, GSM on OMAP3EVM board. > > > > Warm Regards, > > Anil > > > > On Thu, Nov 27, 2008 at 11:56 AM, Nimit Manglick <[EMAIL PROTECTED]> > wrote: > > > Hi Anil / Maxime > > > > > I am also trying my hands on android.. > > > > > I have also ported android on OMAP 35X (from Mistral) .. > > > > > I am getting the home screen with touchscreen working.. > > > > > Now i want to move ahead with some queries :- > > > > > 1. How to enable to Network sso that i can start playing with browser ? > > > > > 2. Can I interface this board with GSM module so that i can have my > call > > > working ? > > > > > 3. Is this released source code have working Bluetooth & WiFi ?? If yes > then > > > what > > > > > changes & where I need to do to make them work (this board doesn't > have > > > bluetooth 7 WiFi support , I am asking for general steps ) > > > > > Thanks & Regards > > > Nimit > > > > > On Thu, Nov 27, 2008 at 11:49 AM, Anil Sasidharan <[EMAIL PROTECTED]> > wrote: > > > > >> Hi, > > > > >> We have ported android-1.0 onto OMAP3EVM (from Mistral) > > >> with 2.6.26 kernel. If you are interested in getting some info/support > > >> on this, please let us know. > > > > >> Warm Regards, > > >> Anil > > >> Mistral > > > > >> Warm Regards, > > >> Anil > > > > >> On Thu, Nov 27, 2008 at 7:34 AM, kapare < > [EMAIL PROTECTED]> > > >> wrote: > > > > >> > Nice I'm happy to speak and exchange with MontaVista guy! > > > > >> > I imagine that your demo with OMAP 3 EVM and montavista src have > been > > >> > ship for Embedded Technology 2008 in Yokohama, Japan, November 19-21 > ? > > > > >> > I'm still wiondering why you used 2.6.24 and not minimally 2.6.25 or > > >> > higher, since android is 2.6.25. > > > > >> > I will try to go with 2.6.22.18 TI src and patch android on it! > > > > >> > thx for infos > > > > >> > kap > > > > >> > On Nov 26, 1:45 pm, Maxime Petazzoni <[EMAIL PROTECTED]> > > >> > wrote: > > >> >> Hi, > > > > >> >> On 26 nov, 18:36, kapare <[EMAIL PROTECTED]> wrote: > > > > >> >> > > No, I've used MontaVista Linux 2.6.24 > > >> >> > > : > http://mvista.com/press_release_detail.php?fid=news/2008/MontaVista-L... > > >> >> > > , on top of which I added the Android drivers (that needed a > bit of > > >> >> > > work because of some differences between 2.6.25 and 2.6.24, > > >> >> > > especially > > >> >> > > in sysfs). > > > > >> >> > Did you get the src code from git our from support of monta > vista? > > > > >> >> > thx for helping a guy a bit lost! > > > > >> >> I work at MontaVista, and the press release up there depicts our > work > > >> >> on Android. We used our kernel as the base for the Android port, so > we > > >> >> already have OMAP3EVM and OMAP3LDP board support. Except from small > > >> >> keypad mapping changes between EVM and Zoom, I only had to rebuild > the > > >> >> kernel for the correct board to move from the EVM to Zoom. I > haven't > > >> >> tested yet, but I suspect it will go as smoothly for the > BeagleBoard > > >> >> as well. > > > > >> >> - Maxime > > > > >> >> > kap > > > > >> >> > On Nov 26, 4:57 am, Maxime Petazzoni <[EMAIL PROTECTED] > > > > >> >> > wrote: > > > > >> >> > > Hi, > > > > >> >> > > On 26 nov, 00:28, kapare <[EMAIL PROTECTED]> > wrote: > > > > >> >> > > > Hi Maxime, > > > > >> >> > > > I have a OMAP3EVM and I'm interested in porting it with > android. > > > > >> >> > > > OMAP3EVM come with OMAP35x_SDK_0.9.5 that contain 2.6.22.18. > > > > >> >> > > > 1- Did you port the kernel to 2.6.25 or just used 2.6.22.18+ > > >> >> > > > android > > >> >> > > > patch - goldfish stuff ? > > > > >> >> > > No, I've used MontaVista Linux 2.6.24 > > >> >> > > : > http://mvista.com/press_release_detail.php?fid=news/2008/MontaVista-L... > > >> >> > > , on top of which I added the Android drivers (that needed a > bit of > > >> >> > > work because of some differences between 2.6.25 and 2.6.24, > > >> >> > > especially > > >> >> > > in sysfs). > > > > >> >> > > > 2- Did you try to directly use the OMAP zoom on a OMAP3EVM, > It > > >> >> > > > seem to > > >> >> > > > work very slow and bugy! > > > > >> >> > > Sorry, I don't understand your question :( > > > > >> >> > > - Maxime > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
