From: Marek Vasut <marex@nabladev.com>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>,
u-boot@lists.denx.de
Cc: Peng Fan <peng.fan@nxp.com>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Sam Protsenko <semen.protsenko@linaro.org>,
Tom Rini <trini@konsulko.com>,
u-boot@dh-electronics.com
Subject: Re: [PATCH V2] board: dhelectronics: imx: Use second Ethernet MAC also from fuse
Date: Fri, 3 Apr 2026 06:43:18 +0200 [thread overview]
Message-ID: <f33fd3f7-fbab-44d4-bce8-e33d8d03b933@nabladev.com> (raw)
In-Reply-To: <20260402143753.40142-1-cniedermaier@dh-electronics.com>
On 4/2/26 4:37 PM, Christoph Niedermaier wrote:
> Currently, the board specific code evaluates only the first Ethernet
> MAC address fuse, regardless of whether the first or second MAC
> address is requested. When the function for determine the second
> Ethernet MAC address is looking for the fused MAC address, it only
> reads the first MAC address fuse and increment it by one to set
> the second Ethernet MAC address. That is not the expected behavior
> when two MAC addresses are fused, because this causes the second
> fused MAC address to be ignored. Change this so that the second
> fused MAC address will be used.
>
> In addition, the handling of the MAC address for early prototypes
> will be removed, as such SoMs were not used by customers.
This ^ should be kept.
> Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com>
> Reviewed-by: Peng Fan <peng.fan@nxp.com>
RB goes above SoB line
[...]
> @@ -84,19 +84,8 @@ static int dh_imx8_setup_eth1addr(struct eeprom_id_page *eip)
> if (!dh_get_mac_from_eeprom(enetaddr, "eeprom1"))
> goto out;
>
> - /*
> - * Populate second ethernet MAC from first ethernet EEPROM with MAC
> - * address LSByte incremented by 1. This is only used on SoMs without
> - * second ethernet EEPROM, i.e. early prototypes.
> - */
> - if (!dh_get_mac_from_eeprom(enetaddr, "eeprom0"))
> - goto increment_out;
> -
> return -ENXIO;
>
> -increment_out:
> - enetaddr[5]++;
> -
> out:
> return eth_env_set_enetaddr("eth1addr", enetaddr);
> }
Please keep this ^ hunk, the rest is fine, thank you.
prev parent reply other threads:[~2026-04-03 4:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 14:37 [PATCH V2] board: dhelectronics: imx: Use second Ethernet MAC also from fuse Christoph Niedermaier
2026-04-03 4:43 ` Marek Vasut [this message]
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=f33fd3f7-fbab-44d4-bce8-e33d8d03b933@nabladev.com \
--to=marex@nabladev.com \
--cc=cniedermaier@dh-electronics.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox