* Gateway AM-GZ80x: Re-brand as Amper & update u-boot to v2024.04
During a search I noticed other companies are using the same
unit. Lets re-brand to Amper as technically that is the product
brand name.
Signed-off-by: Patrick Yavitz <pyavitz@armbian.com>
* Delete old patch set: `patch: u-boot: v2023.10: board_gateway-gz80x`
Signed-off-by: Patrick Yavitz <pyavitz@armbian.com>
* Update test target
---------
Signed-off-by: Patrick Yavitz <pyavitz@armbian.com>
Co-authored-by: Patrick Yavitz <pyavitz@armbian.com>
Co-authored-by: Igor <igor@armbian.com>
* youyeetoo r1 v3: add initial support for this board
* arch: arm64 board: youyeetoo r1 v3 replace edge with vendor kernel
* arch: arm64 board: youyeetoo r1 v3 reviews changes:
- Removed patch, see the pr for more details #7108
- Removed old kernel legacy
- WIP: Added DTS code on https://github.com/armbian/linux-rockchip/pull/223
I compiled the OS with latest changes, untested build logs in https://paste.armbian.com/ofidozaqup
* Update: Rename board from V3 to v3 (ARM64, Youyeetoo R1)
- Note: Untested on v1 as I don't have a v1 board available.
* Discord annoucement: push only when label "Needs review" is set
* Change to label triggering
* actions: Add run-name to `pr-announce` workflow
---------
Co-authored-by: ColorfulRhino <131405023+ColorfulRhino@users.noreply.github.com>
The workflow ran regardless whether `ARMBIAN_SELF_DISPATCH_TOKEN` was set or not, generating errors if the secret could not be found.
In addition, simplify and beautify the workflow.
- one is actually general fix - recommened installation of library before installing rockchip-multimedia
- second is holding package before running upgrade as it wants to pull older library from kde repositories
- remove KDE Neon base files upgrade pin
Reference patch set: https://patchwork.ozlabs.org/project/uboot/list/?series=411513&state=*
Hopefully, other boards using same uboot-version can benefit from the added support.
**Note for Maintainers - to enable KASLR seed, you need:**
- `CONFIG_RANDOMIZE_BASE=y` configured in your kernel .config
- `CONFIG_CMD_KASLRSEED=y` and` CONFIG_DM_RNG=y` configure in your u-boot .config
- exposed crypto and rng nodes in you board's device-tree
- `kasrlseed` command before kernel boot in your boot.cmd
- `CONFIG_SECURITY_DMESG_RESTRICT=y` in kernel .config is also advisable
* KASRL-supported u-boot 2024.07 for everyone:
- move /chosen/kaslr-seed support patchset to general 2024.07 BOOTPATCHDIR
- attach nanopi-r5c and oprangepi5-plus BOOTPACHDIR to patches/uboot/v2024.07 general dir
* u-boot: patch nanopi-r5c-rk3568_defconfig and orangepi-5-plus-rk3588_defconfig to enable KASLR
* rewrite-uboot-patches nanopi-r5c/orangepi5-plus
* patches: uboot: Improve kaslrseed support for v2024.07
---------
Co-authored-by: ColorfulRhino <131405023+ColorfulRhino@users.noreply.github.com>
* rockchip64: edge: rewrite kernel config
* rockchip64: edge: set CONFIG_SECURITY_DMESG_RESTRICT=y
Advised for KASLR-enabled kernels - no side effect for non-KASLR
* rockchip64: current: rewrite kernel config
* rockchip64: current: set CONFIG_SECURITY_DMESG_RESTRICT=y
Advised for KASLR-enabled kernels - no side effect for non-KASLR
