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
6d24f2138b
|
3 years ago | |
|---|---|---|
| .. | ||
| audio | 3 years ago | |
| audio_remote_submix | 3 years ago | |
| camera | 3 years ago | |
| consumerir | 3 years ago | |
| fingerprint | 3 years ago | |
| gralloc | 3 years ago | |
| hwcomposer | 3 years ago | |
| input/evdev | 3 years ago | |
| local_time | 3 years ago | |
| nfc | 3 years ago | |
| nfc-nci | 3 years ago | |
| power | 3 years ago | |
| radio | 3 years ago | |
| sensors | 3 years ago | |
| soundtrigger | 3 years ago | |
| thermal | 3 years ago | |
| tv_input | 3 years ago | |
| usbaudio | 3 years ago | |
| usbcamera | 3 years ago | |
| vibrator | 3 years ago | |
| vr | 3 years ago | |
| Android.mk | 3 years ago | |
| README.android | 3 years 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/.