From: Peng Fan <peng.fan@oss.nxp.com>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Cc: u-boot@lists.denx.de, Marek Vasut <marex@nabladev.com>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Peng Fan <peng.fan@nxp.com>,
Sam Protsenko <semen.protsenko@linaro.org>,
Tom Rini <trini@konsulko.com>,
u-boot@dh-electronics.com
Subject: Re: [PATCH] board: dhelectronics: imx: Use second Ethernet MAC also from fuse
Date: Fri, 20 Mar 2026 23:00:14 +0800 [thread overview]
Message-ID: <ab1g/jhEfgdd6w93@shlinux89> (raw)
In-Reply-To: <20260320102918.4011-1-cniedermaier@dh-electronics.com>
On Fri, Mar 20, 2026 at 11:29:18AM +0100, Christoph Niedermaier wrote:
>When two Ethernet MAC addresses are fused, the first MAC address
>is incremented by one and used for the second MAC address. This
>causes the second fused MAC address to be ignored. Change this
>so that the second fused MAC address will be used.
>Keep the old behavior if there isn't any second Ethernet MAC
>defined and only the first MAC address is fused but not the
>second. In this case use the fused MAC address incremented by
>one, for the second MAC address.
>
>Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
next prev parent reply other threads:[~2026-03-20 14:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 10:29 [PATCH] board: dhelectronics: imx: Use second Ethernet MAC also from fuse Christoph Niedermaier
2026-03-20 13:41 ` Peng Fan (OSS)
2026-03-20 14:41 ` Christoph Niedermaier
2026-03-20 15:00 ` Peng Fan [this message]
2026-03-20 18:22 ` Marek Vasut
2026-03-21 20:55 ` Christoph Niedermaier
2026-03-21 23:40 ` Marek Vasut
2026-03-23 10:07 ` Christoph Niedermaier
2026-03-23 14:58 ` Marek Vasut
2026-03-23 16:49 ` Christoph Niedermaier
2026-03-23 17:20 ` Marek Vasut
2026-03-27 22:02 ` Christoph Niedermaier
2026-03-27 23:11 ` Marek Vasut
2026-03-31 9:19 ` Christoph Niedermaier
2026-03-23 17:34 ` Marek Vasut
2026-03-26 13:34 ` Christoph Niedermaier
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=ab1g/jhEfgdd6w93@shlinux89 \
--to=peng.fan@oss.nxp.com \
--cc=cniedermaier@dh-electronics.com \
--cc=marex@nabladev.com \
--cc=patrice.chotard@foss.st.com \
--cc=peng.fan@nxp.com \
--cc=semen.protsenko@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@dh-electronics.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.