Placing the fips140.ko at the same level as other kernel modules makes
it easier for automation tools to handle all of them.
Bug: 331791671
Change-Id: I7d69226d594fe068a6ccb99bb5a29620468f4aed
Signed-off-by: Qian-Hao Huang <qhhuang@google.com>
assign system_dlkm.modules.blocklist to BOARD_SYSTEM_KERNEL_MODULES_BLOCKLIST_FILE
located from kernel prebuilts folder
Bug: 267429528
Bug: 322457552
Change-Id: I912f1a8e0df12e4614c74b870921ca0b47b8383e
Signed-off-by: Robin Peng <robinpeng@google.com>
- BOARD_SYSTEM_KERNEL_MODULES_LOAD is for GKI modules
- BOARD_VENDOR_KERNEL_RAMDISK_KERNEL_MODULES_LOAD should not contains GKI modules
Bug: 267429528
Bug: 322457552
Change-Id: Ib5da01f861a34edec07e2a958f153c876e5cef10
Signed-off-by: Robin Peng <robinpeng@google.com>
- Include mediacodec_samsung setting from gs-common
- Enable Codec2 HIDL 1.2 from BoardConfig and update
manifest hidl version for samsung.hardware.media.c2
Bug: 318793681
Test: run cts -m CtsMediaDecoderTestCases
Test: run cts -m CtsMediaPlayerTestCases
Test: run vts -m vts_treble_vintf_vendor_test
Change-Id: I1f947d2eb75bd4d75d9db1d39b0b083d32f8032f
a15331d574
Compile ArmNN shim over the support library.
Remove settings for the old HIDL backend.
The new ones will be in the gs-common folder.
Test: Local run of CtsNNAPITestCases
Test: Local run of VtsHalNeuralnetworksTargetTest
Test: Local run of MLTS Benchmark
Bug: 283724775
Change-Id: Ic9f1c26345e52df8b6ef75e2a8261d71a8950c72
This revert was created by Android Culprit Assistant. The culprit was identified in the following culprit search session (http://go/aca-get/123b2665-83ef-4fd0-904d-a0d8c5782db9).
Change-Id: Ib69a94a6a2a8a087e3c2e7e5539045ec751e4a8f
Compile ArmNN shim over the support library.
Remove settings for the old HIDL backend.
The new ones will be in the gs-common folder.
Test: Local run of CtsNNAPITestCases
Test: Local run of VtsHalNeuralnetworksTargetTest
Test: Local run of MLTS Benchmark
Bug: 283724775
Change-Id: I3652eceb14d06a3e909444edc21ad86d9378bc6c
Currently, all gs201 targets have a system_dlkm image but their
modules are stored on the vendor_dlkm partition. In order to
support the staging kernel, modules have to be split across the
system/vendor_dlkm images.
This fix enables targets to define modules on the system_dlkm image.
If so, the system/vendor_dlkm split will be honored. Otherwise, all
modules will remain stored on the vendor_dlkm image.
Test:
- Build and flash aosp_panther, no errors.
- Build and flash a target defining BOARD_SYSTEM_KERNEL_MODULES, ensure
modules are correctly split across the two dlkm partitions.
Bug: 285177263
Change-Id: I80131d97073ce666a9228a47c2fff94b76139a64
Signed-off-by: Samuel Gosselin <sgosselin@google.com>
USE_ANGLE in moved to core.mk across platform, this patch updated the
usage of it in device.mk.
Bug: 270994705
Test: atest CtsAngleIntegrationHostTestCases
Change-Id: I58d57cd5e58d0a4706e8771ffb5e903795954f19
The pvmfw partition is expected to be kept in sync with the system
partition so, instead of having it as a standalone partition (covered by
vbmeta.img), add it to vbmeta_system.
Bug: 275497314
Test: TH
Change-Id: I2ff0fc14b9c9f8cf09907369a82f16d22a8c8297
Add adaptive haptics config parameter to the build environment
Bug: 198239103
Test: atest VibratorHalCs40l26TestSuite
Change-Id: Id2a9e0d346c4722651f9d0a03e7c4f4aa5ac2861
Signed-off-by: Chris Paulo <chrispaulo@google.com>
In aosp, the name of the variable changed from
FORCE_MULTILIB_FIRST_ON_DEVICE to IGNORE_PREFER32_ON_DEVICE.
So actually modify this so the new devices don't have 32 bit
servers.
Test: Verified that drmserver/mediaserver are 64 bit processes.
Change-Id: I282f5129bcc91d99e924f514b01fc4e7e37e9ea9
When $(TARGET_KERNEL_DIR) contains:
* boot.img
then use those as prebuilt boot images for the target build.
Bug: 242812258
Change-Id: I10ccfaacfc77cc37eee085b27575fae515ceb088
Add support for copying prebuilt kernel modules like fips140.ko into the
vendor kernel ramdisk. These kernel modules are different in the following
ways:
- They do not appear in vendor_kernel_boot.modules.load provided by the
kernel build system.
- We want to put their names at the very beginning of the output
modules.load file to ensure that they are loaded prior to all other
modules.
We define a new Makefile variable named
BOARD_PREBUILT_VENDOR_KERNEL_RAMDISK_KERNEL_MODULES. For every filename
on this list, we verify that the file exists in $(KERNEL_MODULE_DIR),
and if it does, we include its name in the modules.load for the vendor
kernel boot ramdisk.
Bug: 194712883
Change-Id: I91a1d834b32717d32621d0a67da9052324cab20c
This variable is always false or empty now.
Remove it so we can mark it as deprecated later.
Bug: 241346584
Test: Presubmit
Change-Id: I110a1e1c07a1debd2c1ce75c70261e62eac8ec5c
Merged-In: I110a1e1c07a1debd2c1ce75c70261e62eac8ec5c
(cherry picked from commit f9b02ea439)
This reverts commit 2ece1b7eb1.
Reason for revert: Platinum/DM rotation revert for likely breaking tests and causing b/253694548
Change-Id: Ie1e5a31b2a094ebec9359906665586c6de6fc882
This variable is always false or empty now.
Remove it so we can mark it as deprecated later.
Bug: 241346584
Test: Presubmit
Change-Id: I110a1e1c07a1debd2c1ce75c70261e62eac8ec5c
Merged-In: I110a1e1c07a1debd2c1ce75c70261e62eac8ec5c
(cherry picked from commit f9b02ea439)
This variable is always false or empty now.
Remove it so we can mark it as deprecated later.
Bug: 241346584
Test: Presubmit
Change-Id: I110a1e1c07a1debd2c1ce75c70261e62eac8ec5c
This is done by conditionally including the makefile under vendor so
that AOSP builds where vendor is not present do not faile.
(cherry picked from commit a3a42642f3)
Bug: 203234558
Test: data wipe in Android recovery mode on raven
Test: data wipe in Android recovery mode on c10
Test: data wipe in user mode fastbootd mode on raven
Test: data wipe in user mode fastbootd mode on c10
Signed-off-by: Jeffrey Carlyle <jcarlyle@google.com>
Change-Id: I0ef9dd1ea9eae90ed4feabd19bf9edc7434a572b
This partially reverts the following change:
Switch GLES system driver to ANGLE
Bug: 241757590
Test: com.google.android.GoogleCamera
Change-Id: I79fee4a16eedf87aea40fd75044e065e1811e117
Revert "move digital car key wiping to gs-common"
Revert "clear secure element of Digital Car Keys during factory ..."
Revert "dck: switch to gs--common implementation of digital car ..."
Revert submission 19734547-b203234558-qpr1
Reason for revert: see b/243864778
Reverted Changes:
I53967a5e8:dck: pick up recovery mode library for digital car...
I8fd944c60:dck: switch to gs--common implementation of digita...
I6e8c80818:move digital car key wiping to gs-common
I60052ca58:Support calling WipeKeys with out a ui object
I459d81800:clear secure element of Digital Car Keys during fa...
Change-Id: Ic3f42d0d2c6c78be47cacf9794e7727e6ee5475f
This is done by pick optionally including a Makefile so that aosp builds
in which the library is not present will pass.
Bug: 203234558
Test: adb reboot recovery; wipe data via menu; verify keys removed
Signed-off-by: Jeffrey Carlyle <jcarlyle@google.com>
Change-Id: I53967a5e8ea0327d6467623929902b90eb2c85da
Actuator models can vary across devices. Actuator models can have
different characteristics that need to be handled appropriately. Add
support to define the actuator model used in Soong makefiles.
Bug: 236202962
Test: verified that different actuator model configs are used on
different targets
Signed-off-by: Chase Wu <chasewu@google.com>
Change-Id: I4b4c5e26c52f410ec36f9b8959e8fadd2ea19b0f
When building the 64 bit and the 32 bit executables, there
are a few targets that are prefer32. Using this option forces
those executables to be built as 64 bit.
Bug: 229787331
Test: With this option, drmserver/mediaserver are built as 64 bit.
Test: Without this option, drmserver/mediaserver are built as 32 bit.
Change-Id: Ie76ffe17f14b5157983796a616436bfa12987136
