diff options
author | Ed Coyne <edcoyne@google.com> | 2017-06-08 12:26:48 -0700 |
---|---|---|
committer | Ed Coyne <edcoyne@google.com> | 2017-06-19 17:27:08 -0700 |
commit | 7464ac9bd7fe89061e47617e4b6004b88c91d636 (patch) | |
tree | 7466478571007709d256f4876cb12cd1ce0aea53 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
parent | 2cb3f59668d9cbb91785feee312fff6945425281 (diff) |
Allow IO During boot process, BootActions.
NOTE: this is only compiled into products with PRODUCT_IOT=true.
Introduce BootActions that a developer can provide to manipulate IO
before the android framework comes up on boot.
We will look for a configuration file at /oem/app/etc/boot_action.conf and
expect it to tell us the name of a shared library. We will then fetch
this library from /oem/app/lib/${arch}/ and load it. We expect it to export
boot_action_init(), boot_action_shutdown(), and optionally
boot_action_start_part(int partNumber, int playNumber).
We will then call boot_action_init() during boot after PeripheralManager
is up and call boot_action_shutdown() when the android framework is up
and we are going to start loading APKs.
We will also call boot_action_start_part(*) when each part of the boot
animation is started, use this if you want to synchronize the boot
action and the boot animation.
Boot actions run in a restricted environment and in general can only
make calls to PeripheralManager.
Bug: 37992717
Test: Pushed to local imx7d to test boot actions, pushed to bullhead test that animation+sound still works.
Change-Id: I9e53a17567f8028ea84486d637e1d231ee1125e1
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions