From e9708b8c335d0462e5ab06fdc5e852faed06caf8 Mon Sep 17 00:00:00 2001 From: Ricardo Pardini Date: Tue, 18 Mar 2025 16:16:51 -0300 Subject: [PATCH] mekotronics-rk3588: u-boot: back to radxa's v2024.03, as .10 breaks GMAC stable MAC patch - this reverts d048673c004f99c715b88ac517736f802c28d572 just for the Meko's - there is little to be gained from .10 anyway on those machines (IMHO) - it is still vendor 2017.09 after all, dunno why Radxa calls them "2024.x" --- .../sources/vendors/mekotronics/mekotronics-rk3588.hooks.sh | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/config/sources/vendors/mekotronics/mekotronics-rk3588.hooks.sh b/config/sources/vendors/mekotronics/mekotronics-rk3588.hooks.sh index e40b017d7..40aa37084 100644 --- a/config/sources/vendors/mekotronics/mekotronics-rk3588.hooks.sh +++ b/config/sources/vendors/mekotronics/mekotronics-rk3588.hooks.sh @@ -8,6 +8,11 @@ function post_family_config__vendor_uboot_mekotronics() { display_alert "$BOARD" "Configuring $BOARD vendor u-boot" "info" declare -g BOOTDELAY=1 # build injects this into u-boot config. we can then get into UMS mode and avoid the whole rockusb/rkdeveloptool thing + + # Override the stuff from rockchip-rk3588 family; Meko's have a patch for stable MAC address that breaks with Radxa's next-dev-v2024.10+ + declare -g BOOTSOURCE='https://github.com/radxa/u-boot.git' + declare -g BOOTBRANCH='branch:next-dev-v2024.03' # NOT next-dev-v2024.10 + declare -g BOOTPATCHDIR="legacy/u-boot-radxa-rk35xx" } # Conditional hook to allow experimenting with this against legacy/vendor branches