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 -~----------~----~----~----~------~----~------~--~---
