Anil, I currently have Mistral OMAP35x EVM (running OMAP3503) and am trying to port android 0.9 to run on it. However, EVM SDK from Mistral/TI is based on 2.6.22.18 and android 0.9 is based on 2.6.25. Mainly, I've been having difficulty applying OMAP35x EVM patch (I created from diff between linux-2.6.22.18 and kernel running on OMAP35x EVM = linux-2.6.22.18+TI mods) to plain linux-2.6.25. Since it looks like you gotten things running on OMAP3430, do you have suggestions or guidance? Thought I should get 2.6.25 going on the EVM, then try applying android patch (I created from diff between linux-2.6.25 and linux-2.6.25-android-0.9_r1).
Any help would be appreciated. twebb On Sep 4, 6:16 am, "Anil Sasidharan" <[EMAIL PROTECTED]> wrote: > Hello Ram, > > On Tue, Sep 2, 2008 at 6:07 PM, Ram <[EMAIL PROTECTED]> wrote: > > > Hi Anil, > > > I able to bring android m5 kernel with m3 file system on omap2430sdp > > with linux kernel 2.6.26. > > Any specific reason for this combo? (m3 FS on m5 kernel?) > > > <http://2.6.26.> > > > 1. i am unable to bring-up m5 file system. my android patch from > > raymond contains driver/android, driver/binder tree structure.. does > > it have any issues? do i need to bring binder.c into driver/android? > > /driver/binder is obsolete, instead use the driver module in driver/android. > This would appear as one of the "misc" devices. > > > > > 2. does it related with frame buffer driver? i haven't modified > > existing frame buffer driver.. > > M5 will not come up without the framebuffer driver supporting double > bufffering > > > > > 3. now currently i am working on omap3430sdp with kernel 2.6.22 from > > TI. where u got the kernl 2.6.24 for omap3430 sdp. > > if i edit raymond patch for omap3430 , will it be OK? pls share > > yiur experience on this? > > I've not tried bringing up Android on OMAP3430-SDP, hence no comments on > that part. However our effort on Mistral's OMAP3EVM (based on 3430) was > successful. You need to turn off the TLS register support while building the > kernel for OMAP3430 platform to support Android as it does not have support > for TLS register up-till Android V09 SDK. (BTW, we have Android v09 up and > running) > > > > > Thanks in advance > > -Rammohan > > Warm Regards, > Anil > > > > > > > On Aug 13, 10:42 pm, "Anil Sasidharan" <[EMAIL PROTECTED]> wrote: > > > On Wed, Aug 13, 2008 at 6:37 PM, Ram <[EMAIL PROTECTED]> wrote: > > > > > Anil, > > > > > please answer following two basic questions: > > > > > 1. does android application starts automatically after kernel calling > > > > init module? OR do we need to run specific android application/ > > > > scripts? > > > > You will have to setup certain environment variables before invoking > > "init". > > > Please refer towww.elinux.org/Android_OMAPformore details > > > > > 2. now i have decided to work with kernel 2.6.23/22. but these kernel > > > > versions doesn't have Omap2430 sdp support. can you please tell me > > > > where i can get the kernel 2.6.22/2.6.23 with omap2430 sdp compliant > > > > OR you have done this exercise for yourself. please let me know any > > > > links available on this. > > > > As I'd pointed out before, I was never successful in bringing up Android > > on > > > OMAP2430SDP and the hardware platform on which Android came up was > > Mistral's > > > OMAP2 EVM. However I guess you should be able to get the 2.6.23/2.6.22 > > > kernel from the omap GIT. > > > > > Thanks in advance.. > > > > > -RamMohan > > > > > On Aug 11, 4:17 am, "Anil Sasidharan" <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > I'm CC-ing this to the group as well as it may help someone else > > > > also > > > > > :-) > > > > > > Please see my answers in-lined with your post > > > > > > On Mon, Aug 11, 2008 at 1:28 AM, roy basavaraju < > > [EMAIL PROTECTED] > > > > >wrote: > > > > > > > *Anil,* > > > > > > ** > > > > > > * i got patch from raymond. but when i tried to patch it with my > > > > working > > > > > > kernel 2.6.26(which is omap2430 sdp compliant), it had undergone > > some > > > > patch > > > > > > errors & mainly it hasn't found omap24xxfb.c file to patch. i got > > this > > > > file > > > > > > from TI site & now i want to patch with this file.* > > > > > > I've never tried applying the kernel patch that I've received from > > > > Raymond > > > > > onto 2.6.26 kernel. My experminets with Android on both OMAP2430 and > > > > > OMAP3430 platforms were done with the following kernel versions: > > > > > (a) 2.6.22 -> OMAP2430 (b) 2.6.23 -> OMAP2430 (c) 2.6.24 -> OMAP3430 > > > > > > Therefore I may not be able to comment on the feasibility of applying > > > > those > > > > > patches on top of 2.6.26 kernel (there might be a lot of API > > changes). > > > > The > > > > > 2.6.24 kernel being supported by TI on Labrador board (OMAP3430 > > platform) > > > > > does have the difference that you have pointed out. I guess from > > 2.6.24 > > > > > onwards the "omap24xxfb.c" replaced with omap_fb.c for OMAP3430 > > platforms > > > > > and omapfb_main.c for OMAP2430 platforms. > > > > > > ** > > > > > > > ** > > > > > > *do i need to mount procfs or just my kernel(2.6.26+omap2430sdp) > > with > > > > > > raymond patch + m5 sdk will bring android default apps onto > > > > omap2430sdp. > > > > > > please clarify do i need to do any kind of modification in m5-sdk.* > > > > > > Yes you have to supprt procfs, tmpfs and sysfs and these need to be > > > > mounted > > > > > before your invoke Android. > > > > > > > ** > > > > > > ** > > > > > > *Thanks a lot anil...* > > > > > > ** > > > > > > *-RamMohan* > > > > > > Warm Regards, > > > > > Anil- Hide quoted text - > > > > - Show quoted text -- 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 [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 -~----------~----~----~----~------~----~------~--~---
