These are required to build. Separate CL to preserve blame history.
From running 'update-includes.sh' script here.
Bug: 37280010
Test: boot/build (sanity)
Change-Id: Id9c2dc37f674b27b947a9f823bd38a550d64d31b
This splits headers into three locations:
include - for backwards compatibility, the global include
include_all - for things system/vendor both use
include_vendor - for things that only vendors use
The goal is to gradually have system things stop referencing
(at least most) of these headers.
Bug: 37280010
Test: build (CL on top adds back in symlinks)
Change-Id: Ibf194276b7faa857e1e7605d7719f4e7d873ecba
hardware/libhardware/include was being included with -isystem, which
hides warnings. Use a macro to convert modules to hw_device_t** to call
the open function that works in C++ and C.
Bug: 32018017
Test: m -j
Change-Id: If68bf15581975f1217fcab366cef7bc784894641
This is useful for the Access-Controlled NVRAM HAL because
implementations may be able to achieve atomic writes if they are able to
limit the maximum space size. This method allows the module to report
that it is imposing such a limit.
BUG=27480753
Change-Id: Ia70f459d7d5fca894e52310ddb2cdcbb51bd8364
This allows inclusion of the new nvram_defs.h header to pull in NVRAM
types and constants without pulling in hardware.h, which is difficult
in low-level environments such as Trusty (and the full NVRAM HAL
header isn't useful in that environment anyways).
Change-Id: I023104ec666832d4e01ae8841a4d6407a5b04643
This HAL abstracts implementations of non-volatile storage with
hardware-backed access controls.
BUG=24397987
Change-Id: Ia9935b138a7ad3e931c54e590570d233c9036e0f
