From: Wolfgang Denk <wd@denx.de>
To: Michal Simek <michal.simek@xilinx.com>
Cc: Michael Walle <michael@walle.cc>, Marek Vasut <marex@denx.de>,
u-boot@lists.denx.de,
Grygorii Strashko <grygorii.strashko@ti.com>,
fried.dev@gmail.com, joe.hershberger@ni.com, sjg@chromium.org,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH RFC] cmd: fix net list command
Date: Mon, 15 Nov 2021 16:20:09 +0100 [thread overview]
Message-ID: <1649664.1636989609@gemini.denx.de> (raw)
In-Reply-To: <2a51974b-41cf-56e4-c9c9-e6b699f27f5c@xilinx.com>
Dear Michal,
In message <2a51974b-41cf-56e4-c9c9-e6b699f27f5c@xilinx.com> you wrote:
>
> As we discussed in previous thread. I think there shouldn't be a problem
> when u-boot passes random mac address (in whatever way) but if Linux
> driver know how to get correct one it should be tried first.
No, I strongly disagree here. If I set a MAC address in U-Boot and
pass it to the kernel, I want that the kernel uses this address.
there may be very good reasons to chose some other address - even if
the "correct" one is known in U-Boot (say, by accident there are
several boards using the same MAC address).
> And it is up to board designer to decide when it is the right time. I
> can imagine that it can be the part of kernel driver or can be purely
> done in user space.
Again, no. It must not be done automatically in the kernel driver,
as this would restrict the user's capabilities to decide what
happens. If the user want's to change the address in Linux, he can
do this in user space - but again, it is then a (hopufully concious)
decision of the user, and not some automagic code in a driver which
ruins all my attempts to use the address I want to have used.
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
Perfection is reached, not when there is no longer anything to add,
but when there is no longer anything to take away.
- Antoine de Saint-Exupery
next prev parent reply other threads:[~2021-11-15 15:20 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 [this message]
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
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=1649664.1636989609@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