I would suggest you to have a look of the overlay code in hardware/libhardware/moudule/overlay. In the new HAL architecutre, it introduced a "stub" concept which replaced the legacy architecture which load the c/c++ library from java application/service directly. In "stub", you need to implement some interfaces and provide them to hardware service. For example if you wanna implement a LED, the architecture will be:
Kernel Driver (driver to control the LED hardware) <-> syscall (open, close, ioctl for LED, etc.) <-> hardware/libhardware/module/led (the led HAL interfaces or "stub" ) <-> framework/base/services/jni/ com_android_server_LedService.cpp (the java native interface for LED )<-> framework/base/service/java/com/android/server/LedService.java (the java interface of LED service <-> framwork/base/core/java /android/hardware/LedManager (the java code of LED manager) and ILedService.aidl (the android interface description language file for LED) <-> LED application 2010/8/23 Techie <[email protected]> > Hi All, > > I would like to know if there is any documents or related web links > for device driver development on "User Space Abstraction Layer ". > I would appreciate if anyone can give me how this really works in > real world scenario. > > Thanks... > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
