You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
hmz007
36ed224bac
|
1 year ago | |
|---|---|---|
| .. | ||
| audio | 1 year ago | |
| audio_remote_submix | 1 year ago | |
| camera | 1 year ago | |
| consumerir | 1 year ago | |
| fingerprint | 1 year ago | |
| gralloc | 1 year ago | |
| hwcomposer | 1 year ago | |
| input/evdev | 1 year ago | |
| local_time | 1 year ago | |
| nfc | 1 year ago | |
| nfc-nci | 1 year ago | |
| power | 1 year ago | |
| radio | 1 year ago | |
| sensors | 1 year ago | |
| soundtrigger | 1 year ago | |
| thermal | 1 year ago | |
| tv_input | 1 year ago | |
| usbaudio | 1 year ago | |
| usbcamera | 1 year ago | |
| vibrator | 1 year ago | |
| vr | 1 year ago | |
| Android.mk | 1 year ago | |
| README.android | 1 year ago | |
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 /vendor/lib/hw/ and have a well defined naming
convention:
/vendor/lib/hw/<*_HARDWARE_MODULE_ID>.<ro.product.board>.so
/vendor/lib/hw/<*_HARDWARE_MODULE_ID>.<ro.board.platform>.so
/vendor/lib/hw/<*_HARDWARE_MODULE_ID>.<ro.arch>.so
/vendor/lib/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/.