* rename .dts sources in overlay directory as *.dtso
* change "target +=" line in "dts-y +=" in overlay Makefile
* remove "always +=" line in overlay Makefile
* add .scr compilation support in kernel scripts/Makefile.lib
* patch kernel scripts/Makefile.dtbinst to avoid flattening overlay
directory
for the last two points, see
general-add-overlay-compilation-support.patch
- makes it compatible with vendor out-of-box blobs (which include TEE) in the from-factory eMMC
- Armbian itself doesn't ship TEE blobs
- when combining from-factory eMMC blobs with an Armbian SD card, TEE blobs are in practice found by u-boot
- but then proceeds to fail with `optee api revision is too low`
- disable OPTEE in defconfig fixes it, TEE isn't used in any way by Armbian
- makes it compatible with vendor out-of-box blobs (which include TEE) in the from-factory eMMC
- Armbian itself doesn't ship TEE blobs
- when combining from-factory eMMC blobs with an Armbian SD card, TEE blobs are in practice found by u-boot
- but then proceeds to fail with `optee api revision is too low`
- disable OPTEE in defconfig fixes it, TEE isn't used in any way by Armbian
uboot default behaviour is the assert resets when
it has to pass control to the kernel.
This may cause compatibility issues if the kernel
driver is not instructed to properly deassert the resets,
so we change the uboot behaviour for dwc and ehci usb
drivers to deassert reset on exit.
multitool utility uses the legacy/vendor 4.4 kernel
and it was failing to turn on HDMI properly.
Assert and deassert all vop and hmdi resets to clean
up the state on uboot exit seems to solve the issue
- we've had kernel patches/DT (from chewitt) for this in meson64 for a long time, but I never sent the board
- uses blobs for the `tartiflette-s912` which is also an DDR3 S912 (VIM2's blobs are DDR4 and won't boot)
- this adds `u-boot 2024.04` support, using chewitt's DT & `000.patching_config.yaml` & a specific BOOTPATCHDIR
- this is a full board as-if it was an SBC, and expects to boot from mainline u-boot;
- for that to work you've to wipe the eMMC and get rid of the vendor-supplied u-boot
- if this is not what you want/need, you can use the aml tvbox "board" instead, together with Android u-boot
