platform_hardware_libhardware/modules
Mathias Agopian e25e1969dd get rid of overlay HAL
Change-Id: I1ba7ffac8776a8d59a5cc4e7688c3a5bd02e6647
2011-07-12 15:48:30 -07:00
..
audio Audio HAL: added interface for audio preprocessing 2011-07-08 09:59:52 -07:00
gralloc Remove workarounds for buggy /dev/fb0 drivers 2011-06-06 13:28:45 -07:00
hwcomposer remove deprecated/unused HAL headers 2011-04-28 20:09:45 -07:00
Android.mk libhardware: add stub audio and audio_policy modules 2011-04-27 14:08:57 -07:00
README.android auto import from //depot/cupcake/@135843 2009-03-03 19:32:14 -08:00

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/.