7518109063
ADF isn't a candidate for upstreaming and isn't (directly) usable from unprivileged NDK code, so it makes more sense to keep video/adf.h as a private header inside libadf, where it'll still be usable by HWC implementations without shipping in the NDK. libadf exports its entire include/ directory, so this shouldn't have any impact on HWC implementations that already link against libadf. Test: mmm system/core/adf/libadf Test: /data/nativetest64/adf-unit-tests/adf-unit-tests (on Nexus 9) Change-Id: I6573f539cfd7fc65433237d0b115b8b7b2728133 Signed-off-by: Greg Hackmann <ghackmann@google.com> |
||
---|---|---|
.. | ||
scsi | ||
uapi/linux | ||
README.TXT |
The files under the uapi directory are android kernel uapi header files that exist in android kernels, but have not been upstreamed into the regular kernel. None of these files will get updated automatically, and are frozen at their current value. The files under the scsi directory are frozen copies of kernel scsi headers. Linux's scsi headers are a mix of userspace-facing and kernel-facing declarations that can't be directly used by userspace. The glibc maintainers manually copy-and-pasted these definitions into their own scsi headers and haven't substantially updated them in 15 years. The musl libc project has a similar set of definitions in its scsi headers. These files are actually maintained in external/kernel-headers/modified/scsi. Any modification should first be made there then copied into the scsi directory.