From: Michael Walle <michael@walle.cc>
To: monstr@monstr.eu
Cc: d.antliff@unsw.edu.au, seanga2@gmail.com, u-boot@lists.denx.de,
Michael Walle <michael@walle.cc>
Subject: Re: Setting MAC address from I2C EEPROM - debug / commands? (Xilinx)
Date: Wed, 23 Nov 2022 14:27:30 +0100 [thread overview]
Message-ID: <20221123132730.2083267-1-michael@walle.cc> (raw)
In-Reply-To: <5381fce5-7227-9920-5956-4ce33e4d0070@monstr.eu>
>> ethernet {
>> nvmem-cells = <&mac_address>;
>> nvmem-cell-names = "mac-address";
>> };
>>
>> You'll need 2022.07 for this I think. This is the same method which
>> Linux uses. I added this specificly to be able to load MAC addresses
>> from EEPROMs without needing to hard code stuff into Kconfig.
>
> This looks good and I see Sean wired it in the U-Boot already. It should work
> fine with all Xilinx formats but on boards just for MAC address. (FRU format is
> also designed in a way that the same boards have MAC address at the same location).
> The code I described above is also checking in FRU format that checksums are
> correct and also reading more information from it for other use cases.
You might also be interested in the new NVMEM layout patch series:
https://lore.kernel.org/lkml/20221118185118.1190044-1-michael@walle.cc/
-michael
next prev parent reply other threads:[~2022-11-23 13:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 1:23 Setting MAC address from I2C EEPROM - debug / commands? (Xilinx) David Antliff
2022-11-23 3:14 ` Sean Anderson
2022-11-23 8:45 ` Michal Simek
2022-11-23 13:27 ` Michael Walle [this message]
2022-11-23 15:11 ` Michal Simek
2022-11-23 15:26 ` Sean Anderson
2022-11-23 22:14 ` David Antliff
2022-11-23 21:56 ` David Antliff
2023-06-12 3:25 ` David Antliff
2023-06-12 4:01 ` Sean Anderson
2023-06-12 4:16 ` David Antliff
2023-06-12 5:32 ` David Antliff
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=20221123132730.2083267-1-michael@walle.cc \
--to=michael@walle.cc \
--cc=d.antliff@unsw.edu.au \
--cc=monstr@monstr.eu \
--cc=seanga2@gmail.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.