| Age | Commit message (Collapse) | Author |
|---|
|
Unfortunately it has never worked particularly well due to missing
driver support and it was getting in the way of some refactoring. The
maintainers have indicated that they intend to continue maintaining
it out of tree.
Bug: 217455793
Change-Id: I2a659a980d32912bec5a1c0869c88e06a29cf9ce
|
|
Now that lcd_density is made device-specific, add it for Pixel3.
Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
Change-Id: Iab08a8b9ea6f8fbc1cdb8d04bc957ef9404e2292
|
|
fstab.common was updated to add virt a/b and slotselect; pixel3 is not
quite ready for it, so temporarily make it device specific and remove
slotselect for now.
TODO: revert this while adding virt a/b support.
Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
Change-Id: Iaaada81e2d2fbdaca2ee630eb61422adaedbbb1d
|
|
The maximum size of all dynamic partition groups should not exceed
the super size - DAP metadata size. Today the configuration of
the device doesn't take the metadata into acount.
Since we recommend 4M to partners, reserve 4M here.
Bug: 183360400
Bug: 182431975
Change-Id: Idd6d01db2594b4598c03aecbf931009fcf92a36c
Test: TH
|
|
Bug: 173737347
Test: treehugger
Change-Id: Id49741240ecfe74aa006e58540c16a4b0d8b8ff4
|
|
The overlayfs remount handling of superpartitions expects the
fstab to have all the partitions in it.
This means we can't use the split between the ramdisk fstab
and the vendor fstab that we have been previously.
So this patch merges the two fstabs together.
With this change "adb root; adb remount" works now.
Signed-off-by: John Stultz <john.stultz@linaro.org>
Change-Id: Iad408d5d3b1e4c9291a947cd44ee65f4aaef5c45
|
|
This adds some changes to get the pixel3_mainline target
building a boot.img. It requires that a pixel3_mainline dir be
present in the dragonboard-kernel dir, and it should contain
a Image.gz-dtb file and any kernel modules to be included.
If you do not want to use kernel modules, build with
PIXEL3_USES_GKI=false.
This is take number two, as the first pass was causing build
breakage. In this version, I check to make sure we have a
kernel image before we try to build.
In v3, I've moved some more modules as vendor-only, to allow
the pixel3 to boot.
Signed-off-by: John Stultz <john.stultz@linaro.org>
[sumits: updated the list of vendor-only modules]
Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
Change-Id: Ie94ef4af00c415baeb20838cb0ba30434efa691e
|
|
In aosp/master, GetFstabPath funtion defined here:
https://android.googlesource.com/platform/system/core/+/refs/heads/master/fs_mgr/fs_mgr_fstab.cpp#411
and the fstab.ramdisk.common does not need to be copied to vendor partition.
Test: boot up pixel3 with mainline kernel: it mounts all partitions correctly, and boots to 'UI',
also: VtsKernelEncryptionTest#FileBasedEncryptionTest passed 3/3
Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
Change-Id: I5a0e3058d0b580aff06bfea1a01eeb666ce14182
|
|
This allows including firmware files extracted from stock, if available,
to be included into the build.
Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
Change-Id: I8c3ac09472a01cb0ac52e2e734993711cd409d93
|
|
boot.img"
This reverts commit 85f6a8aecd3ba7609d28ace79f474a411092ebdd.
Reason for revert: Caused build-break for aosp-master (pixel3_mainline-userdebug build)
Change-Id: I653961de83baa953cfdde32e42d5706869764d9a
|
|
This adds some changes to get the pixel3_mainline target
building a boot.img. It requires that a pixel3_mainline dir be
present in the dragonboard-kernel dir, and it should contain
a Image.gz-dtb file and any kernel modules to be included.
If you do not want to use kernel modules, build with
PIXEL3_USES_GKI=false.
Change-Id: Iacea2afd0c81d65935de7e52bb680d2e314f6b3c
Signed-off-by: John Stultz <john.stultz@linaro.org>
|
|
Boots Blueline (Pixel3) to console. Graphics broken
due to missing drm, panel driver and firmware files.
Change-Id: Ibd3df4e03f093ec34b7f3eb5f6394a0a811ce139
Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
|
