From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] net/eth: Don't issue warnings for offboard ethernet chips
Date: Mon, 19 Dec 2011 18:55:42 +0100 [thread overview]
Message-ID: <20111219175542.4BFAA138EE40@gemini.denx.de> (raw)
In-Reply-To: <58A08F2D-4743-4634-A909-466EB853570B@boeing.com>
Dear "Moffett, Kyle D",
In message <58A08F2D-4743-4634-A909-466EB853570B@boeing.com> you wrote:
>
> > Yes, it should. The rule is that then environment settings always
> > have precedence, and if they are missing or contain different data
> > than other sources for this information, a waning shall be printed.
>
> That is a problem for devices which are typically add-in PCI cards.
> In that case U-Boot can't be expected to have knowledge of what the
> MAC addresses should be, and it should just use the ROM attached to
> the card instead.
The user can be expected to read the boot messages and adjust the
environment if he wants to use the card's settinge. In any case, the
user shall have the authority to overwrite the card's settings by
defining any settings in the environment he wants.
> In our use case the e1000 chips are on a separate board attached via
> CompactPCI. U-Boot should not spontaneously start throwing errors
> just because the board was stuck into a different slot or replaced
> due to hardware failure.
U-Boot does not throw errors if you have appropriate settings in the
environment. The worst to happen is a warning thatt he MAC settings
in U-Boot and on the card don't match.
> However, in the case that the board itself has a valid external MAC
> address and U-Boot does not even have an environment variable, it
> should not cause extra messages. Think about hot-pluggable USB net
> adapters where the detection order is nondeterministic.
Yes, it should, because a mandatory environment variable is not set
correctly.
> The "e1000" driver has always done that. I can submit a separate
> patch to fix that if you would like.
Thats would be welcome, thanks.
> Ok, I will respin the patch so that errors show up like this:
>
> Net: eth0, eth1,
> ERROR: Could not set MAC address: 00:50:93:81:ff:8a
> eth2
>
> Is that OK?
Yes, thanks.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Two wrongs don't make a right, but three rights make a left.
prev parent reply other threads:[~2011-12-19 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 2:17 [U-Boot] [PATCH] net/eth: Don't issue warnings for offboard ethernet chips Kyle Moffett
2011-12-17 20:16 ` Wolfgang Denk
2011-12-19 16:41 ` Moffett, Kyle D
2011-12-19 17:55 ` Wolfgang Denk [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=20111219175542.4BFAA138EE40@gemini.denx.de \
--to=wd@denx.de \
--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