Changes to align with standard beagle images.
- extlinux.conf is much more flexible than uEnv.txt, specially when
having multiple kernel for development - menu entries are valuable for recovery
- typical beagleboard Debian images have been using extlinux.conf for
a while.
Signed-off-by: Ayush Singh <ayush@beagleboard.org>
Co-authored-by: Andrei Aldea <7153954+Grippy98@users.noreply.github.com>
using this extension allows for activation of the APA armbian package
archive and installation of the provided binary packages at image
creation time from within the Armbian Build Framework.
The goal of APA is to simplify maintenance of Armbian Core by moving
dependency logic and other packaging information into a separate space
and handle that meta-data with the proper distribution-creation and
-publication tools. Currently, much of this is done with fragile bash
scripting in Armbian Core instead.
https://github.com/armbian/apa
- **CHANGE**: This version tries to boot SD first (thus SD -> USB -> NVMe -> eMMC); before it would boot USB before SD
- as Armbian u-boot is possibly deployed to SPI, try to make as compatible as possible; eg enable squashfs support
- enable `setexpr` and `fileenv`, used by HAOS
- HAOS already has support for booting VIM3 from NVMe: https://github.com/home-assistant/operating-system/pull/3784
- borrowed `fileenv` patch from v2025.01 to .04
- Similar treatment that `odroidm1` got in https://github.com/armbian/build/pull/7769
- note: I will be leaving my VIM3 behind in the other side of the globe, so this is my last chance to test
* Update rock-4se.csc
Update the version of U-boot used with rock 4 se.
Tested locally on my board after building an armbian image.
ubuntu@rock-4se:~$ strings /dev/mmcblk1 | grep U-Boot
U-Boot SPL 2025.04-armbian-2025.04-S3482-P4a0b-H3d34-Va9af-Bb703-R448a (Apr 22 2025 - 10:05:17 +0000)
U-Boot phase
U-Boot
FIT image for U-Boot with bl31 (TF-A)
* Use BOOTCONFIG="rock-4se-rk3399_defconfig" and remove BOOTPATCHDIR
* Removed old comment
* Update rock-4se.csc
Revert BOOTCONFIG and update BOOT_FDT_FILE="rk3399-rock-4se.dtd"
* Update rock-4se.csc
Set BOOTCONFIG="rock-4se-rk3399_defconfig"
When RTL8152 USB network is enabled as build-in, it will throw out warnings such as:
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153b-2.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-3.fw for built-in driver r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for built-in driver r8152
This should prevent this while keep driver as module.
I don't know. This doesn't feel right. The package exists in Jammy, Noble and Bookworm in both amd64 and arm64 variants so should be good...though it is probably not needed in all constellations.
Still it is part of the toolchain and not generic packages. If this gets merged as it is this should be revisited.
