I had an email exchange with our partner support group and updated documents are in the works. I can't give you a timeframe yet.
In the meantime, if you have specific questions, this is the right place to ask. There are a number of different porting efforts in various stages, so there's a good chance that someone will have run into a similar problem. On Nov 18, 8:54 pm, Pivotian <[EMAIL PROTECTED]> wrote: > it will be my pleasure to update the porting guide, but i am still > stuck at some point and moreover i am not clear about the whole > porting steps itself. But i f i get a start up i will surely update > the Porting guide. > > On Nov 18, 10:11 pm, "[EMAIL PROTECTED]" > > <[EMAIL PROTECTED]> wrote: > > If it's important to you, perhaps you might volunteer to update the > > porting guide. > > > On Nov 17, 8:29 pm, Pivotian <[EMAIL PROTECTED]> wrote: > > > > The Porting Guide is out of date now because google has released the > > > entire source code itself. Since its been long time that google > > > released the source code why don't google release an updated porting > > > guide so that it becomes easier for lots of engineers around the world > > > who are planning to port thr android on rela time hardwares. > > > > On Nov 17, 9:54 pm, "[EMAIL PROTECTED]" > > > > <[EMAIL PROTECTED]> wrote: > > > > The HAL exists because some hardware mfgrs don't want to open source > > > > all of their code. I think the PDK documents describe most, if not > > > > all, of the required porting activities. If you follow the emulator > > > > model and put all the driver code in the kernel, you should be able to > > > > use the existing HAL implementation. > > > > > On Nov 17, 4:22 am,Pivotian<[EMAIL PROTECTED]> wrote: > > > > > > I am planning to port the Android on the real time hardware. The > > > > > Android structure contains the linux kernel and some applications. The > > > > > linux kernel is in the folder "kernel". we can easily create the image > > > > > by building the kernel or running the makefile of the kernel. We then > > > > > load the kernel image to the memory of the hardware along with > > > > > mounting of its file system. And we will boot from that memory > > > > > location , the board will boot up and it will show the command prompt > > > > > of the linux kernel. Upto this everything seems fine. But my confusion > > > > > is, this is not the end of porting. There are some more things outside > > > > > the kernel folder like the video codecs are in the folder "external/ > > > > > opencore/codecs_v2/video" like wise some audio codecs, some codes > > > > > related to RIL and many more. My question is how to port all these > > > > > additional stuffs like userspace HAL,java applications etc to the > > > > > board after successful porting of kernel? --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
