Hi, For the high level stuff, I made a brief post around this topic. Please see if you find it useful: http://sujaiantony.wordpress.com/2012/06/25/an-android-101-hardware-and-hal/
The ti-wiki page I mentioned in the Reference section has a nice step by step explanation on writing a new driver. thanks Sujai. sujaiantony.wordpress.com On Mon, Jul 2, 2012 at 6:42 PM, Thomas Moore <[email protected]>wrote: > Hi guys, > > I have a fairly high level question about the steps to go through when > adding a new device driver. From what I can tell, drivers consist of a > kernel portion and then a shared library in the AOSP that gets used by the > HAL. What I am > wondering is how the HAL accesses the *.so libraries. If I was to add a > new camera driver for example, do I need to name it libcamera so that it > gets picked up by the HAL or is there a way to specify a new name and link > it in? > > Also can applications access the hardware directly or do they always need > to go through the higher level services? For example, if I were to add a > new kind of sensor, do I need to somehow add this in to the sensor service > to use the APIs in my app > or can I do a dlopen() and interact with the hardware that way? > > Thanks! > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-porting > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
