[PATCH RFC] cmd: fix net list command

Tom Rini trini at konsulko.com
Mon Nov 15 16:45:16 CET 2021

On Mon, Nov 15, 2021 at 04:25:55PM +0100, Wolfgang Denk wrote:
> Dear Tom,
> In message <20211115151956.GN24579 at bill-the-cat> you wrote:
> > 
> > Well, what I mean is, where are the real MAC addresses?  What is the
> > rationale for setting NET_RANDOM_ETHADDR?
> One practical use case is board provisioning in the factory, which
> includes setting up valid produt data like serial number, MAC
> address etc. Yes, this can be done over serial consone as well, but
> 1) this is slower than network and 2) many commecial products don't
> have the connector etc. populated.

Is that the case for the layerscape or imx8 families?  I know on the TI
side these values are derived from chip-specific fuses that are blown at
chip production so we don't need an initial random one.  I'd have to
pull up some NXP manuals to see what's the case there, but I think some
other people on the thread know the answers here already.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20211115/4e2ef42d/attachment.sig>

More information about the U-Boot mailing list