- Disable dlkm ramdisk fragment from vendor_boot
- Enable vendor_kernel_boot and OTA support
- Set partition size to 64MB
Bug: 214409109
Change-Id: I4a6ee0b2f1c44a4d257cc51cf408f6f7cf295471
Signed-off-by: Lucas Wei <lucaswei@google.com>
As HW doesn't have 32 bit address limitation, we can disable
zone dma32 to simplify memory management and improve performance.
Bug: 224535283
Test: boot, test basic wifi, faceauth, camera, UDFP features
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: Ia7c1098ddd4b91738702dd99552661dbe18cfaa5
This reverts commit 184562c0f8.
Reason for revert: The cache coherency shouldn't be reverted. This will cause the function break.
Change-Id: I9a62e507911a3eaed704f029546e81770ef3d199
Since GRALLOC_VERSION control has been totally removed, the
corresponding conditional configs should be removed to avoid wrong
configurations.
Bug: 224911573
Test: gralloc sync function can work to avoid noise in tiktok
Change-Id: I7d48f0271a251dfef2abc13dea59b92c541a497e
This will let bionic use 8.2a atomics which helps scudo locking.
Bug: 224756824
Test: build , boot and check by getprop
Change-Id: Ie5f55071af5b8aff293224665ca68942f3e86625
Keep 2MB swiotlb for devices that not support 36bit access.
Bug: 226578178
Test: boot
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: I88deb288e326880b0328c06f5d1b32777cc1ccb9
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: 223663549
Change-Id: If9d2b1041108cec8fc0481e4b633502371d6f987
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: 207573157
Test: check total memory and io_tlb_nslabs
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: I21eac64f57505c14e12fed50980aad4d818b34cb
Enable page pinner to catch long pin pages' history so
we can root cause issues.
Bug: 224771748
Test: check kernel cmdline
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: I3b384d427ac0ba48841d9a13e8f5565d9a83fb72
Pixel kernel don't use MEMCG, let's disable it to
minimize the overhead.
Bug: 224521042
Test: check cmdline
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: I60681fb04e4f9a41814eda5988b6c1a0d4fb127c
Set flags to enable system_dlkm dynmaic partition
for GKI Modules for T launch pixel devices.
Partition will be empty as of now but this adds
enough support to pass the vts for feature.
Bug: 222334390
Test: TH, manual build, Code testing gs101 & R6
Signed-off-by: Ramji Jiyani <ramjiyani@google.com>
Change-Id: Ic56dd711ab97f3ae993cc5c543fabc8cbe3f347c
Merged-In: Ic56dd711ab97f3ae993cc5c543fabc8cbe3f347c
Builds a new init_boot.img with the ramdisk that was previously in
boot.img.
Removes the ramdisk from boot.img.
Change fstab to make sure the /dev/block/by-name/init_boot_* entries are
created in first stage init for Verified Boot.
Add init_boot.img to the list of OTA images so it is picked up for OTA
updates.
Test: unpack_bootimg --boot_img=boot.img
Test: unpack_bootimg --boot_img=init_boot.img
Test: Build and boot new device with required bootloader changes
Bug: 211823573
Merged-In: Idbd700b17d862f48ea568d1274a6550b965763ea
Change-Id: Idbd700b17d862f48ea568d1274a6550b965763ea
The pvmfw image is included by setting PRODUCT_BUILD_PVMFW_IMAGE in
device.mk and there shouldn't be this prebuilt override.
Bug: 199717422
Test: build
Change-Id: I0ba022e7b222ff89a4b2f991900abb3b4589396c
This file contained incorrect commented-out conditionals that
were apparently copied and pasted from somewhere. Fix them to
match gs101 configuration.
Bug: 212047904
Test: build master-without-vendor
Change-Id: Ibecd05d6e5cf1ee94be57203b63c6aec3cab8aa6
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: Ia9994121309a8a0e5a664b64c51ffb3ad9110747
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
and switch to TARGET_RECOVERY_FSTAB_GENRULE.
Bug: 201700692
Test: m RBC_BOARD_CONFIG=1 nothing on gs201 products
Change-Id: I74bf8700161f6519d29b2b3634a286c4e758d136
Remove option for _64 and default to 64-bit only builds.
Removes the (out of date) manifest_64 files.
Removes OMX since it is not supported for 64-bits.
Bug: 213924541
Test: Build, Boot, YouTube playback, Play store, Camera
Signed-off-by: Pat Tjin <pattjin@google.com>
Change-Id: I1e97903b598a2fff46d912a009b2bc73f1b0f466
Add a file "fstab.gs201-fips" alongside the existing "fstab.gs201" in
order to specify different encryption settings in FIPS mode.
"androidboot.fstab_suffix=gs201-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.
(cherry-pick from device/google/gs101)
Test: Boot to home screen with/without fips mode
Bug: 202417706
Signed-off-by: Konstantin Vyshetsky <vkon@google.com>
Change-Id: I8fdc1c9a91399816fa2d4c53f282d63e988ce7d5
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: 192241728
Change-Id: I05d55f8a2854619b92defcf3fb11cc2b87a8dab6
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: I6fc41a0143e7253f193cac509ba30506feb4e2d9
They aren't needed for first-stage boot, and can be loaded from
`/vendor` and `/vendor_dlkm`.
Bug: 189506395
Test: boot to home
Change-Id: Ib4c708c8631586cf25e1535035b8bc81f727ef5f
