Remove redundant spaces so the variable is set correctly
Bug: 224556677
Test: Built R4 64bit
Signed-off-by: Gina Ko <yichunko@google.com>
Change-Id: Ide1f48cf04806234f637faea5edcd988403bafca
Set flags to enable system_dlkm dynamic partition
for GKI Modules for gs101 devices.
Partition will be empty as of now but this adds
enough support to pass the vts for the feature.
Bug: 222334390
Test: TH, manual build, flash and verification on 6Pro
Full OTA Update test from S to T as below:
1. go/flash: git_sc-v2-release - SP2A.220405.004 (8233519)
2. Full ota build from tm-dev
3. Manual push full ota update and verify boot
4. Verify system_dlkm partition is present & mounted
Signed-off-by: Ramji Jiyani <ramjiyani@google.com>
Change-Id: I0b4038b100add965737527b72a8d5f905907e23e
Some targets are using tangor_xxx and some use xxx_tangor,
cover both to avoid duplicate zygote props.
Test: Build
Signed-off-by: Pat Tjin <pattjin@google.com>
Change-Id: I43b18f6b5296f7b1575a8d5e817b3f2281dc1e1c
Moving vendor_dlkm.modules.blocklist to the source repo and picking to
/<DEVICE>-kernel, the development experience can be aligned between
Kernel and Android codebase.
Bug: 214017561
Change-Id: I9f556178f882dc15cc7066df16dd59e1da86091b
intermediates-dir-for relies on several variables that
haven't been set at the time the board configuration
runs. The board configuration got around that by using
deferred expansion, but deferred expansion is something
that starlark doesn't support. Remove intermediates-dir-for
by switching to TARGET_RECOVERY_FSTAB_GENRULE, which
accepts a genrule module to use instead of a file.
Bug: 201700692
Test: Presubmits
Change-Id: I6ebb75073abeebce71873f414129759789096b0f
move wifi configurations from BoardConfig-common.mk to wifi/BoardConfig-wifi.mk.
So, each project can decide whether it should share the same configurations or create a new one on their own.
Bug: 208159314
Test: ifconfig after attempting STA+SAP concurrency.
Change-Id: Id2474df377f242528be661fefe712d7203cdddf8
As dma devices are 36bit bounded, we don't need SWIOTLB
bounce buffers. Set swiotlb=noforce to disable this and
make the minimum amount of memory allocation.
Bug: 205246642
Test: check total memory and io_tlb_nslabs
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: If9f68b269f326f0f4b8e165593ec5dd4787fbb52
Remove the definition for BOARD_PREBUILT_PVMFWIMAGE (which currently
points to the shared AOSP pre-built of pvmfw.img) to fall back to the
default behavior of the AOSP framework. Even though this will result in
the same pre-built being used (for now), not setting that variable still
partially modifies the overall behavior (e.g. for packaging) and allows
upcoming framework changes to be automatically picked up.
Bug: 199717422
Test: m
Change-Id: I7c3bbbee8c83d262b707f8582b5f43040bc25a06
Remove the deprecated variable now that it has been replaced by
BOARD_PVMFWIMAGE_PARTITION_SIZE in AOSP.
Bug: 199717422
Test: m ${ANDROID_PRODUCT_OUT}/pvmfw.img
Change-Id: I96fba129d0b0f9a2e845e8a507a9ec8f65910942
Support for pKVM is being added to all gs101 builds starting with T,
disabled by default. So far, the userspace components have been included
only in special _pkvm builds. Include them unconditionally.
Also move BOARD_* variables specifying location and partition size of
pvmfw from vendor board config file here.
This adds 89MB to the size of the system image.
Bug: 192819132
Test: build a gs101 target, check /apex/com.android.virt exists
Change-Id: Ie46b0ad5f45bd4757570b72cb275d002df7b4616
This reverts commit 7badc4b5f1c7b6adff8cd9142f5c97bd4a5a0d49.
Reason for revert: it introduce b/201469630 and b/201476061
Bug: 201469630
Bug: 201476061
Change-Id: Id48ea931410a55bfd382feb7a0da02994fdf8928
When $(TARGET_KERNEL_DIR) contains:
* boot.img
* boot-user.img
then use those as prebuilt boot images for the target build.
Note that debug kernels (e.g. $(TARGET_KERNEL_DIR)/kasan) only have
Image.lz4, so the debug build ends up building boot.img from source.
Bug: 199997188
Change-Id: I6bb70644d8ab7356986f6ca6a77f3098d1ee0f83
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: 195894512
Test: verified that different actuator model configs are used on
different targets
Change-Id: Ic7fd5f52c3bfed252fa3956f3e926c90c1632013
Add a file "fstab.gs101-fips" alongside the existing "fstab.gs101" in
order to specify different encryption settings in FIPS mode.
"androidboot.fstab_suffix=gs101-fips" on the kernel command line will be
used to select the FIPS fstab when needed.
As the two fstabs should be otherwise identical, generate them from a
template file so that they will stay in sync.
Note that generating the fstabs requires that they be installed as build
system modules rather than via PRODUCT_COPY_FILES, which results in the
vendor_ramdisk copy of the fstabs being installed to system/etc rather
than /. This shouldn't cause any problem, now that Android has been
updated to look for the fstab in this location too.
Bug: 191417025
Change-Id: I1d115e014df8ba2fb83046ac0b9b791597364846
This reverts commit 96007d8f9cab5f6028cb4a1b15e30c6ffe8bf5dd.
Temporarily revert prebuilt boot.img usage on sc-qpr1-dev
until we have official signed GKI boot images available.
Bug: 188095549
Bug: 191417025
Change-Id: I2f9907d3674f8a8869aac3c926994e116c76a91b
Use:
* boot-user.img for -user builds
* boot.img for -userdebug and -eng builds
Bug: 188095549
Test: make dist (oriole-user)
Test: make dist (oriole-userdebug)
Change-Id: Ic4df227f2b4c261297272f17e6645b7ce1f5d4f3
This reverts commit 63ba0cb1affa83446f10585d403c81cc618be71a.
Reason for revert: Tentatively trying to address, http://b/193588301 OTA full package does not exist in O6/R4_SD1A.210714.001 userdebug build [SD1A]
Bug: 193588301
Change-Id: I9d5d9fc132bc7eaf7c0adccee7a18558d80edb40
Use prebuilt GKI boot.img for production builds.
Debug builds continue to use their own Image.lz4.
Bug: 191764119
Change-Id: I2b4950ce334cc990e858e0ea410ad7e57d6decf6
All devices use gralloc4 now, so this code is unused.
Bug: 174998182
Test: builds for the affected devices
Change-Id: Icff36a0204f7f9fd10ae7269248aef8a08c5fc1e
This library is hooked into the recovery code via
hardware/google/pixel/recovery and contains routines specific to the
GS101-based hardware.
Bug: 182508814
Test: did master reset on device with keys, verified no keys present after reset
Signed-off-by: Jeffrey Carlyle <jcarlyle@google.com>
Signed-off-by: Harpreet Eli Sangha <eliptus@google.com>
Change-Id: I18357f5ac8db7a765a5464fd3366af3d14928ce6
Revert "recovery: enable support for device-specific WipeSe impl..."
Revert "clear secure element of Digital Car Keys during factory ..."
Revert submission 14983788-clear_keys
Reason for revert: b/192373955
Reverted Changes:
Ia8fc29e6c:add gs101-specific recovery library
Icc1eabfd4:clear secure element of Digital Car Keys during fa...
I943d97b26:recovery: enable support for device-specific WipeS...
I15c7fbd7f:allow recovery and fastboot to access secure elmen...
Change-Id: I545698bc7da1aa12f520c0190775358dae70de61
This library is hooked into the recovery code via
hardware/google/pixel/recovery and contains routines specific to the
GS101-based hardware.
Bug: 182508814
Test: did master reset on device with keys, verified no keys present after reset
Signed-off-by: Jeffrey Carlyle <jcarlyle@google.com>
Change-Id: Ia8fc29e6c043c58c09f189ac5dc91c4093cf64b6
In this commit, we update the interface combination
for P21.
Bug: 191020902
Test: local test on PP23935602 build.
Check STA+STA, STA+SAP, STA+P2P and STA+NAN are workable.
Change-Id: I424c4ea854f3a4f7b615038db8d63729fd32adda
Kernel modules on the blocklist are not automatically loaded during
second stage init. Modules are often put on the blocklist if we want
them to get loaded only under certain circumstances.
Bug: 190652328
Change-Id: Ib67463555f498f4dc85d5d175e0bf9e4150771dd
Previously, we copied all available kernel modules into the vendor_boot
ramdisk except for approx. 14 modules that we explicitly excluded.
Going forward, the kernel build will distribute the two additional files
vendor_boot.modules.load and vendor_dlkm.modules.load which define,
respectively, the lists of modules that should be loaded from
vendor_boot and vendor_dlkm.
The contents of the two *.modules.load files will be copied almost
verbatim into modules.load files in the respective images except for the
fact that the directory names of the .ko files are stripped. So, for
example, kernel/net/core/pktgen.ko becomes just pktgen.ko.
Additionally, we only copy those .ko files into the vendor_boot image
that are listed in vendor_boot.modules.load. On the other hand, the
vendor_dlkm partition image will contain all .ko files regardless of
whether they are listed in vendor_dlkm.modules.load.
Bug: 190652328
Change-Id: Ibda5b9368547ad089575333e2566697ec0e8465f
Enable Page Pinner.
Bug: 187552095
Test: adb bugreport <zip> and confirmed it contains page_pinner
information at dumpstate_board.txt
Signed-off-by: Minchan Kim <minchan@google.com>
Change-Id: I509c5a825a798d8f1851cb65c5dd28dbddf11d33
