tequilaOS/platform_hardware_libhardware
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
platform_hardware_libhardware/modules
History
Mathias Agopian f96b2064d7 remove all references to pmem and simplify the lock/unlock hooks 
this gralloc module is only used on the emulator or without a h/w
renderer. therefore there is no synchronization to do in lock/unlock
and pmem buffers are not relevant.

hopefully this will remove some of the confusion about how gralloc
should be implemented and make it more obvious that this implementation
is not intended to be used by h/w renderers.
2009-12-15 15:00:57 -08:00
..
gralloc remove all references to pmem and simplify the lock/unlock hooks 2009-12-15 15:00:57 -08:00
overlay Integrate from //sandbox/mathias/donut/...@145728 2009-04-10 14:24:31 -07:00
README.android auto import from //depot/cupcake/@135843 2009-03-03 19:32:14 -08:00

README.android 

Default (and possibly architecture dependents) HAL modules go here. 


libhardware.so eventually should contain *just* the HAL hub
(hardware.c), everything in it should be rewritten as modules.

Modules are .so in /system/libs/hw/ and have a well defined naming
convention:

    /system/libs/hw/<*_HARDWARE_MODULE_ID>.<ro.product.board>.so
    /system/libs/hw/<*_HARDWARE_MODULE_ID>.<ro.board.platform>.so
    /system/libs/hw/<*_HARDWARE_MODULE_ID>.<ro.arch>.so
    /system/libs/hw/<*_HARDWARE_MODULE_ID>.default.so

They also have a well defined interface which lives in include/hardware/.

A module can have several variants: "default", "arch" and "board", and they're
loaded in the "board", "arch" and "default" order.
The source code for the "board" variant, usually lives under partners/...

The source code for "default" and "arch" would usually
live under hardware/modules/.