In submitting the original patches for WeTek Hub/Play2 I appear to have squashed an experimental change to place the u-boot.dtsi file on the common board dtsi, but this was incorrect and results in broken Ethernet. Patch 1 creates per-board u-boot.dtsi files to fix that. However, while the NIC is now probed correctly this results in random MAC addresses. Setting the p200 family in board configs also does not work, so patch 2 revises (overwrites) the board init function using the same code as VIM3 which reads the factory MAC from efuse correctly, and patch 3 sets board family to ensure boards have a static MAC. The alternative would be to create a dedicated board definition for wetek boards. If that would be preferred, let me know and I can rework the changes to do that. And apologies for the mistake on the original submission.
Christian Hewitt (3): ARM: dts: fix Ethernet on WeTek Hub/Play2 ARM: board: meson: update efuse MAC reading code configs: amlogic: set board family to avoid random MAC on WeTek Hub/Play2 arch/arm/dts/meson-gxbb-wetek-hub-u-boot.dtsi | 14 ++++++++ ...tsi => meson-gxbb-wetek-play2-u-boot.dtsi} | 0 board/amlogic/p200/p200.c | 35 +++++++++++-------- configs/wetek-hub_defconfig | 1 + configs/wetek-play2_defconfig | 1 + 5 files changed, 37 insertions(+), 14 deletions(-) create mode 100644 arch/arm/dts/meson-gxbb-wetek-hub-u-boot.dtsi rename arch/arm/dts/{meson-gxbb-wetek-u-boot.dtsi => meson-gxbb-wetek-play2-u-boot.dtsi} (100%) -- 2.34.1