From: Christian Hewitt <christianshewitt@gmail.com>
To: u-boot@lists.denx.de, u-boot-amlogic@groups.io,
linux-amlogic@lists.infradead.org
Subject: [PATCH 0/3] ARM: dts: fix Ethernet and random MAC's on WeTek Hub/Play2
Date: Sat, 16 Mar 2024 13:54:27 +0000 [thread overview]
Message-ID: <20240316135430.826898-1-christianshewitt@gmail.com> (raw)
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
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2024-03-16 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 13:54 Christian Hewitt [this message]
2024-03-16 13:54 ` [PATCH 1/3] ARM: dts: fix Ethernet on WeTek Hub/Play2 Christian Hewitt
2024-03-18 8:44 ` neil.armstrong
2024-03-16 13:54 ` [PATCH 2/3] ARM: board: meson: update efuse MAC reading code Christian Hewitt
2024-03-18 8:48 ` neil.armstrong
2024-03-16 13:54 ` [PATCH 3/3] configs: amlogic: set board family to avoid random MAC on WeTek Hub/Play2 Christian Hewitt
2024-03-18 8:50 ` neil.armstrong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240316135430.826898-1-christianshewitt@gmail.com \
--to=christianshewitt@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=u-boot-amlogic@groups.io \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox