We will be changing AB to be the default, existing non-AB targets
need to explicitly set AB_OTA_UPDATER to false
Test: th
Change-Id: I86a76296937a6abab1b4495cd66a35144348aafd
* CTC's 2018 u-boot is more feature-complete for nx for now.
* We may revisit this later.
* This remediates issues with RAM carveout, clocks
(on erista models), mod chip issues (on mariko models),
and brings us almost in-line with L4t releases for nx.
Change-Id: I622cc67acb543b6ac54c8ee7a585d88e8066606c
* Reduce crashing and other issues resulting from density
disagreements. Also, AAPT should not be set as per cuttlefish
and newer Pixel devices.
Change-Id: Ibca27b4a77c84f2e57a534da10c278c7d0f0cf91
* As per cuttlefish etc. and cypress/nxp reference, set overlays for
MAC randomization support. Also enable
WIFI_HIDL_FEATURE_DUAL_INTERFACE and
WIFI_AVOID_IFACE_RESET_MAC_CHANGE as per cypress/nxp reference.
Change-Id: I5ad1539e400d9f79fce641faf284246743b08915
* I don't like this, but adding the required allowances for wifi_reset
results in few insurmountable neverallows.
Change-Id: I6fa3f0cfc62b253c0f30399a3d54b26a5426b855
As of Android 14 QPR2, galen Lineage release key fingerprints are
longer than 92 characters. This cause crashes on prop read. So,
hardcode a default that is shorter than 92 characters, so it can be
overridden later.
Change-Id: I47abbac4344252262c47b865fbda871559fcbf30
* Was tested on odin, modin, frig, and vali.
* Note: Due to the various sensors configurations across SKUs,
sensors will likely need additional labeling after test release.
Change-Id: I0f8b159acc0ae14e8e4c7d8ec29a0cb406d3bff8
* We are aren't launched with Android at all to, but
our partitions were origianlly set up to match
foster, as it is our closest hardware counterpart.
* Those partition sizes are now to small to fit
almost any form of GMS.
* The fact that users have to exploit their console,
run a custom first stage bootloader (Hekate), and
applications bootloader (u-boot) that we control
means that instead of retrofitting dynamic partitions
we can just _launch with them_ (as we have yet to ship
this device).
* Treat this device as if it has always had dynamic
partitions and let Hekate set us up to reflect that.
* Do away with SAR in the process, as Hekate can turn
that off.
* Nuke MDA, we don't support hardware backed encryption
anyway, so it doesn't make any sense to house.
Reference: https://github.com/CTCaer/hekate/pull/922
Change-Id: I1e5d8c309d08559873ea3c93ac5b4b6e197b528e
* Ensure users are always on the latest recovery image
Signed-off-by: Jarl-Penguin <jarlpenguin@outlook.com>
Change-Id: I033ac4442622b737639d678993daf602a89f9bac
* Sadly in PRODUCT_PROPERTY_OVERRIDES this
translates to 3 seperate props, example:
```
bluetooth.device.default_name=SHIELD
Android
TV
```
* The build system flips out when quotes are
used.
* Can't move whole device to *.prop because we
ifdef so many of these in tegra trees that it
would be disgusting.
Change-Id: I4c611c64652d28f65505382db7b3e08bc6f3fabf
* This allows infra to sign successfully, I hate it, but it builds,
boots, and works fine enough as a workaround.
* The underlying issue is that this flag causes avbtool args and location
to be set in `misc_info.txt` whereas before it was not.
Change-Id: I7bdf237ec30d692c7d8b5c626a6e761e2c1a2593
Lineage has switched to clang for kernel builds by default. The
nvidia 4.9 kernel does not build with clang.
Change-Id: Ie00632002a532a7a090d50c1951575c361244f7d
We are migrating from coreboot to an ATF loader
built into hekate-ipl. This will load sc7 bins etc. along
with ATF (bl31) and U-Boot (bl33), which will chainload
kernel (as is currently the case). This also migrates to new
R2P method/driver as the new loader/ATF will stash a
copy of the bootloader in RAM so we do not have to
load a hekate payload.
Change-Id: I11e4a1810829ab3ac4c8830fd03afd6054e40bad
* This is really only needed on devkits to allow
recovery flashed to `LNX` as opposed to `SOS` to
actually boot.
Change-Id: I238f356a0bee74ba2b6b60168d3b072ad490a796
* This is a tree for all Nintendo Switch variants:
`odin`, `modin`, `vali`, and `frig`.
* `ro.hardware` will be NX on all variants with
`ro.hardware.sku` being set per variant by u-boot.
Changes are as follows:
* At the moment the packaged DTB is only for `odin`, more to follow.
* Note: We may make `modin`, `vail`, and `frig` device-tree-overlays
on the `odin` base DTB to simplify things.
* Use darcy's thermal config as it's the most lenient, and is a same SoC STB.
* Unlike `icosa_sr` previously did, we will use the BCM HAL for BT over
BTLinux, as A2DP is tested and verified, no need to deviate.
Changes that will require follow-up commits to build out:
* Update init to reflect nx's needs - will need more work to support devices
other than `odin`.
Removals are as follows:
* Remove all non-nx device support files.
Co-authored-by: Thomas Makin <halorocker89@gmail.com>
Co-authored-by: Billy Laws <blaws05@gmail.com>
Co-authored-by: Aaron Kling <webgeek1234@gmail.com>
Co-authored-by: CTCaer <ctcaer@gmail.com>
Co-authored-by: John Smith <nemui3353@gmail.com>
Co-authored-by: langerhans <langerhans@users.noreply.github.com>
Co-authored-by: Nolen Johnson <johnsonnolen@gmail.com>
Change-Id: I9bab4d94c6e94a9c6e2a7cf04d16c4b76c0b6ac5
* 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
For simplicity, refactor TARGET_TEGRA_KERNEL to contain the decimal
point, and pass that to NV_BUILD_KERNEL_OPTIONS.
Change-Id: I08311ab07358cdd1d6e180dac8230f22f8de317c
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
The kernel build scripts don't support a recovery specific variant
defconfig, so this needs to be a full defconfig
Change-Id: I52d4b423e782894effb619020995a4c2b46ef4f2
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
Kelvin Zhang
LuK1337
tmakin
Nolen Johnson
Aaron Kling
Michael Bestas
Jarl-Penguin
Arne Coucheron
Jan Altensen