From: Wolfgang Denk <wd@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: Michael Walle <michael@walle.cc>, Marek Vasut <marex@denx.de>,
u-boot@lists.denx.de,
Grygorii Strashko <grygorii.strashko@ti.com>,
Michal Simek <michal.simek@xilinx.com>,
fried.dev@gmail.com, joe.hershberger@ni.com, sjg@chromium.org
Subject: Re: [PATCH RFC] cmd: fix net list command
Date: Mon, 15 Nov 2021 16:25:55 +0100 [thread overview]
Message-ID: <1650296.1636989955@gemini.denx.de> (raw)
In-Reply-To: <20211115151956.GN24579@bill-the-cat>
Dear Tom,
In message <20211115151956.GN24579@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.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
How many Unix hacks does it take to change a light bulb? Let's see,
can you use a shell script for that or does it need a C program?
next prev parent reply other threads:[~2021-11-15 15:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 12:11 [PATCH RFC] cmd: fix net list command Michael Walle
2021-11-15 12:15 ` Marek Vasut
2021-11-15 12:24 ` Michael Walle
2021-11-15 13:17 ` Marek Vasut
2021-11-15 13:46 ` Michael Walle
2021-11-15 14:31 ` Wolfgang Denk
2021-11-15 14:52 ` Michael Walle
2021-11-15 14:57 ` Michal Simek
2021-11-15 15:07 ` Tom Rini
2021-11-15 15:22 ` Wolfgang Denk
2021-11-15 15:38 ` Tom Rini
2021-11-15 15:20 ` Wolfgang Denk
2021-11-15 16:12 ` Michal Simek
2021-11-16 13:29 ` Wolfgang Denk
2021-11-15 15:12 ` Tom Rini
2021-11-15 15:15 ` Michael Walle
2021-11-15 15:19 ` Tom Rini
2021-11-15 15:25 ` Wolfgang Denk [this message]
2021-11-15 15:45 ` Tom Rini
2021-11-16 13:23 ` Wolfgang Denk
2021-11-15 15:15 ` Wolfgang Denk
2021-11-15 15:21 ` Michael Walle
2021-11-15 16:45 ` Marek Vasut
2021-11-16 6:14 ` Ramon Fried
2021-11-16 13:33 ` Wolfgang Denk
2021-11-16 14:10 ` Tom Rini
2021-11-16 14:51 ` Wolfgang Denk
2021-11-15 13:57 ` Tom Rini
2021-11-15 14:53 ` Michael Walle
2021-11-15 14:53 ` Michal Simek
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=1650296.1636989955@gemini.denx.de \
--to=wd@denx.de \
--cc=fried.dev@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=joe.hershberger@ni.com \
--cc=marex@denx.de \
--cc=michael@walle.cc \
--cc=michal.simek@xilinx.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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