This reverts commit 7a692d2c.

Change-Id: I4c900cc508a04a2d20240418da045a7e0607f800

Wireguard was merged in kernel 5.6, thus not needed on 5.10 or newer

Change-Id: Ic89ab82666c33bd7a76cd5038f1f82b16d3424fc

Change-Id: I625fc0efd754bd5032d1d89b6062482f47877e56

Sebastiano Barezzi authored Jun 20, 2022 and Aaron Kling committed Jul 01, 2022

Change-Id: Ia9e41028c44f7e8812657115d6a41b4c3ce481f4

Sebastiano Barezzi authored Jun 17, 2022 and Aaron Kling committed Jul 01, 2022

Change-Id: I00ea82b8112546eceb274d1d156fb168c845754a

Sebastiano Barezzi authored Jun 17, 2022 and Aaron Kling committed Jul 01, 2022

Change-Id: I92411f5c0d1ff6cf6555906d9b1c3e2e115d8ca2

Change-Id: I4f8de01c915ea2a97de23b609b95bbe5d7a2c3e0

Change-Id: I5d5eb6d8aa1a57cf8b5ad3920878824667496103

This will not be used by lineage

Change-Id: Ifa65fe1d8c28311cca360eed0c269923feeea4a1

Change-Id: Ib454c965590f7aa7f5aa264255a01a02385a2579

Netflix content using h265 corrupts badly. Removing h265 secure
support makes netflix fall back to h264. This has the unfortunate
effect of removing 4k support from netflix, but working is better
than not working.

Change-Id: I96280968a75bbc76946dc2f4d0d9fb465ff185ad

Change-Id: I57589fd9d47379f02db8ae8eca82a5459c4e5a67

Icosa has not been fully forked yet

Change-Id: I0d13129a9b178479068ec77276203c7113a4363c

Nolen Johnson authored Apr 14, 2022 and Aaron Kling committed Apr 25, 2022

* Allows us to conditionally drop sif support when TV GMS is
  included, which sif has no hope in fitting the full version
  of.

Change-Id: I4ad8ac851fc12d53622a107fe9ed0acf6c102067

Change-Id: Iff4dd7034e4a9a3f35646bd19eed5ce5b4928e2c

For simplicity, refactor TARGET_TEGRA_KERNEL to contain the decimal
point, and pass that to NV_BUILD_KERNEL_OPTIONS.

Change-Id: I08311ab07358cdd1d6e180dac8230f22f8de317c

This has not had an updated fork yet

Change-Id: I2f3055271542b312fc1e5cbfd3e9056b9a2fc34b

The main kernel will no longer depend on anything. Source the odm
driver repos and the relevant kernel dt repos.

Change-Id: Ifb6025d908647a5ef22c989d3ec3ba5360cd2444

Change-Id: I7e88f0e67dc6ee7e20afa5e95c6ea843987529ad

USB configfs is now set at build time by tegra-common
Recovery usb init was simplified

Change-Id: Ie424b5d9359b43fd4f64894720d01026a361f8c5

These are no long necessary as twrp is using by-name paths

Change-Id: I73cbeeaec1020826ba5730582f458e967f43320f

New twrp will not work with legacy fstab format. Also switch to
by-name paths and remove the fstab symlinks.

Change-Id: I403497698f1b6b7cd232081cdb083c82079551a2

TeamWin is now targeting aosp to build twrp. Make a separate target
to allow differentiating twrp and normal aosp. Include the lineage
makefile for the unified build flags. The other flags wont apply
when only building recovery

Change-Id: I8d067b50d02d6e20e8865bdc4dcc414dd73b4c4b

The previous limit was set based on sif per the rel-30 BoardConfig,
which doesn't match the production sif partition layout. This is
updating the size to match the consumer hardware.

Change-Id: I0abb65140e2f52a1c57223fd95bd62db1a45a53a

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

Recovery doesn't know how to format an emmc type partition, causing
failures on data wipe

Change-Id: Ifd32707a3647a8a5119b70adc6109f2e3f22e04d

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

This config is used for encoder tuning, setting bitrates for nvenc

Change-Id: Ib0de6557ecda8ececc0b461a72313d873a3db583

The encryptable path to MDA was missed in the orginal commit

Change-Id: Id99db12d915e3b1c463e9a970bb78541243f6f37

Change-Id: Ib670f50b1d3dc119453ae8bc3f578cc7e482eece

Quallenauge authored Oct 08, 2020 and Aaron Kling committed Mar 21, 2022

Some variants of this target were launched with Android L (kernel 3.10).
This causes the BpfUtils to not use bpf.
Since we upgraded to kernel 4.9, this detection doesn't work,
but on R there's an switch, set via property ro.kernel.ebpf.supported
to force enable 4.9 bpf mode.

Change-Id: I263e3aaa5a9a63cd027d8750c7cad0f34f432ed2

Change-Id: I59330c3853fc0ad6c9f5ee7d9c61ca680b1a6945

Change-Id: Ied419aa8b576805493fafdc1637ad5b81521f911

Reboot to payload will use a copy of hekate stored in reserved ram

Change-Id: Ieeb7a97aa86cd0becff5ff5aff4d12a70519a6d7

Nolen Johnson authored Feb 17, 2022 and Aaron Kling committed Mar 02, 2022

* No longer on foster/darcy/mdarcy stock 8.x or 9.0.0.

Change-Id: I4b4e347a3a6c1ea40b6926bea08bba80a93c2390

Nolen Johnson authored Feb 17, 2022 and Aaron Kling committed Mar 02, 2022

* `PRODUCT_PROPERTY_OVERRIDES` now tosses things on
  `/vendor` by default. We need to dictate where they
  should end up.

Change-Id: I4fa9639f127ec54d5e7d015db5b804815b43dfde

As of stock 9.0, all shield android tv variants ship with aptX

Change-Id: Iea5099d7494fd93bcb2b1737650412bbe5ec4c50

Involves splitting the audio policy for atv and mobile targets

Change-Id: If05aa56e60fd33831768cbe89cd3280895325bd7

Change-Id: I8f2423d075257b260b2e2162f9373c1073ba3885