README.android

模块化HAL在Android设备上的实现与加载顺序

最新推荐文章于 2023-03-31 16:47:32 发布

weixin_30608503

最新推荐文章于 2023-03-31 16:47:32 发布

阅读量53

点赞数

CC 4.0 BY-SA版权

文章标签：移动开发

原文链接：http://www.cnblogs.com/Ph-one/p/4315975.html

本文详细介绍了Android系统中HAL模块的概念、结构、命名规范以及它们的加载顺序，包括如何将源代码组织成不同类型的模块（如默认、架构、板级模块），并阐述了模块之间的依赖关系和加载顺序。

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