Commit Graph

6 Commits

Author SHA1 Message Date
Ricardo Pardini
54c896e029 rk3588: configure UEFI_EDK2_BOARD_ID for all UEFI-supported boards
- 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.
2023-11-19 22:31:33 +01:00
Ricardo Pardini
ea30a06236 mekotronics: refactor vendor conf/hooks; vendor uboot with new patches; new blobs
- meko: don't use Radxa's Rock-5A u-boot anymore, switch to rockchip vendor next-dev branch
- meko: my own (horrible) patches for MAC address stability / defconfig
- meko: cherry picked a few patches for getting rid of BL32/read Bl31 from env and other fixes from Radxa
- meko: add OTP node to 3588 dtsi (so we don't need kern-dtb in ITS for working OTP)
- meko: refactor common code across 3 (soon to be 4) board files into vendor conf and hooks
- meko: bump DDR/BL31 blobs for all Meko boards
2023-07-01 14:53:34 +02:00
hzyitc
e189c104c2 Introduce the BOARD_MAINTAINER in board config (#5159)
* 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>
2023-06-19 17:30:35 +02:00
Ricardo Pardini
5f458c9183 mekotronics (all boards): use new bluetooth-hciattach extension 2023-05-24 19:22:22 +02:00
amazingfate
df3c7eb461 use the same patch dir for u-boot from radxa 2023-05-15 17:12:20 +02:00
Ricardo Pardini
d7a6f80c81 rockchip-rk3588: add new board mekotronics-r58x.wip (Mekotronics R58X) 2023-04-24 14:23:21 +02:00