* Again, we do not plan to support vali display hacks for the
time being. If so, we will add env and do it that way.
* filter-out CEC for vali because common trees assume that unified
devices will all support CEC or none.
Change-Id: I1df0d895de870a3ebd76825fe278997e83435922
Mdarcy was only split because mdarcy/sif would not boot a recovery
image that did not have a dtimage in the recovery-dtbo slot, while
foster would not boot an image that did have that. As of rel-shield-r,
cboot on foster_e models does ignore the recovery-dtbo slot, so there
is no longer a need for the mdarcy shim target.
Change-Id: If4ed56aad54883fc48be86247d2527316fc8f5b2
Somehow, this does not break widevine and other drm on any target
but sif. Even though this keystore contains updated widewine keys
among others.
Change-Id: I262a9fa82659372a896dddd3c391d08a1f02a89a
Selinux is preventing loading kmods in recovery. Since boot and
recovery kernels are now separate, necessary drivers will be built
into the recovery kernel.
Change-Id: I75bab3f3bd03f7fe520af6992afd0b85979f2ede
The foster and loki e00 models will not boot the current nvtboot,
thus are not supported by these builds.
Change-Id: I94e03f19e10be9a9481c1a32543c33a1e688520c
Mdarcy and sif due to recovery requiring a builtin dtimage. Porg
due to requiring signed boot images.
As a result of sif not being installable, switch system and vendor
partition sizes to the next smallest variant, which is foster.
Remove dtimage handling, that will be added directly to the mdarcy
shim.
Change-Id: Ibc7cd0ad2e99d03b3be9dcbc545b2dffa49d05ce
T210B01 cboot uses dt images instead of a single dtb. Build these
images. These cannot be packaged and installed, since the bootloader
blob updates would overwrite it during the subsequent boot. However, they
are useful for testing purposes.
Copy relevant individual dtbs somewhere releasetools can access them.
Change-Id: I387a102912266debe75bfa3b1c4262010bfe0202