* Add BOARD_VENDOR to board configs
* Add BOARD_VENDOR to all board configuration files
- Added BOARD_VENDOR variable to board configuration files
- Using lowercase vendor slugs (e.g., friendlyelec, radxa, xunlong)
- Set 'generic' for boards without clear vendor match
- TV box files (.tvb) excluded as they have no clear vendor
- Enables better board categorization and vendor-specific handling
* Manual adjustements on top of AI matching
* Drop doubled definition and add retroid vendor
* cleanup comments, linebreaks...
* two more comments
* `BOOTFS_TYPE` has never been set as far as I can see, therefore no need to unset.
* some more comments...
* comment, simplify logic
* even more comments
* just a few more
* comments, description for elish
* merge uboot functions. @SuperKali review
* tools: shellfmt: Beautify and add board configs to formatting list
* Format the whole code using `lib/tools/shellfmt.sh`
---------
Co-authored-by: Igor <igor@armbian.com>
- in practice:
- boards that didn't specify their own blobs: bump DDR 1.08->1.16 ; BL31 1.28 -> 1.45 (example: rock-5b!)
- boards that specified 1.16/1.45 individually now follow the defaults (no change)
- boards that specified a different version: no change; just a TODO suggesting review/removal/go-with-the-defaults
- Mekotronics boards: bump from 1.11/1.38 to defaults (1.16 / 1.45)
* 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
- From https://github.com/edk2-porting/edk2-rk3588/releases/tag/v0.9.1
- For example, for `rock-5b_UEFI_Release_v0.9.1.img`
- `UEFI_EDK2_BOARD_ID` is `rock-5b`
- **Important**: this has no effect unless optional extension is enabled
- to test this out:
- make sure to read carefully the instructions at https://github.com/edk2-porting/edk2-rk3588/blob/master/README.md
- suppose you previously built the regular u-boot version with:
- `./compile.sh BOARD=rock-5b BRANCH=legacy RELEASE=jammy`
- now you can build the UEFI version with:
- `./compile.sh BOARD=rock-5b BRANCH=legacy RELEASE=jammy EXT=uefi-edk2-rk3588`
- write the produced image to SD or eMMC and boot it
- use normally, or enter "UMS" mode by selecting that option in the grub menu
- You can write image to eMMC, boot it, enter UMS, write it again to NVMe, reboot, press <ESC> in UEFI and boot from NVMe
- Also works if .img is written to eg USB stick, and UEFI edk2 is separately deployed to SPI flash
- **Important**: make _absolutely_ sure you are able to force Maskrom mode (by shorting pins, pressing buttons, etc) before writing an UEFI image to eMMC; UEFI has no RockUSB ("Loader mode" support) at all. The new "initramfs-usb-gadget-ums" extension hopes to address this, but it is not guaranteed to work.
* Introduce the `BOARD_MAINTAINER` in board config
Yes, we have documented the maintainers in `armbian/documentation`.
But it seem like that some of them don't maintain anymore.
Use a separated repos make us forget to update it.
So let's document here.
What's more, defining this make us easier to update `.github/CODEOWNERS`
* Set `BOARD_MAINTAINER` accroding to `armbian/documentation`
* Guess `BOARD_MAINTAINER`
Set he/she as board maintiner if he/she:
1. Create the board config
3. Commit at lease 3 times for the board config
3. Commit most for the board config
* Guess `BOARD_MAINTAINER`
Set he/she as board maintiner if he/she:
1. Create the board config
2. The only one to commit for the board config
* Set `BOARD_MAINTAINER` to empty for other boards
* AR-1712 fixing PR from wrong DB
* Fixing maintainers
Signed-off-by: Igor <igor@armbian.com>
* Add variable to missing ones
---------
Signed-off-by: Igor <igor@armbian.com>
Co-authored-by: Rafal-Hacus <68160861+Rafal-Hacus@users.noreply.github.com>
Co-authored-by: Igor <igor@armbian.com>
* [ rockchip64] second round config migration
Recommend all @armbian/boards-rockchip maintainers double check the resulting configurations, as stated in the PR the level of confusion in the family config logic likely means some boards have unnecessary extra stuff.
