- add `pre_config_uboot_target` hook for switching BOOTCONFIG across the two targets
- adapt `UBOOT_TARGET_MAP` to not call the defconfig Makefile targets directly, instead, just do a variable assignment (ignored by Make)
- otherwise, when using the defconfig directly in the `UBOOT_TARGET_MAP`, the `post_config_uboot_target` .config changes are overwritten when Make is called
- only patch left is boot usb-nvme-scsi/sata first (still done in meson64.h)
- remove FIP handling from family file `meson-sm1.conf` into board file hook where it belongs
- u-boot: enable more compression methods, EFI debugging, i2c, leds, tcp networking
- use flashcp for mtd writing
- Unchanged:
- confirmed as of v2024.04: using the C4 (not HC4) defconfig is still needed to be able to write to mtd when booted from SD
- also confirmed: one still needs to erase Petitboot using Petitboot, then boot from SD, to be able to flash mainline u-boot to mtd
- exclusive for edge / Kwiboo:
- enable UMS / RockUSB and other gadget stuff
- enable TCP networking features, wget etc
- enable EFI debugging stuff
- store environment in SPI
- uses preboot to flash led briefly
- this code pattern is becoming copypasta fast and needs refactor before it spreads too much
- also for all branches (legacy/vendor/edge):
- nanopct6: updated blobs to DDR v1.16 and BL31 v1.45
- 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
Ethernet is supposedly broken by design.
While Xunlong is working on a hw revision of this board it is to be expected that it will be released under the same name which will then ultimately contribute to users confusion why on some boards eth works and on others not. Therefore get rid of this one altogether.
* Add initial support for the Orange Pi 5 Pro
* Enable MotorComm network driver in rk35xx legacy and vendor kernel config
* Resolve conflicts
---------
Co-authored-by: Igor Pecovnik <igor@armbian.com>
* Odroid C1 received some update
* Zero 3W is maintained by Radxa
* Rock5 itx will be platinum
* Plus version nobody mentioned - save some build resources
* Enabled rock5c
* Enable other two rock5
* Adjust testing targets
