From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2 v2] net, fec_mxc: only setup the device enetaddr with eeprom value, if ethaddr is not setup
Date: Wed, 31 Mar 2010 02:07:54 -0400 [thread overview]
Message-ID: <201003310207.56010.vapier@gentoo.org> (raw)
In-Reply-To: <4C070C16.5000001@denx.de>
On Wednesday 02 June 2010 21:57:42 Heiko Schocher wrote:
> Actual fec_mxc.c driver is *not* correct, because if in eeprom
> is a correct mac, it *always* programms this in the mac address
> registers from the chip!
>
> This is not OK, and must be fixed!
i agree 100%
> > 2. Read from environment in net/eth.c after initialize()
> > 3. Give priority to the value in the environment if a conflict
> > 4. Program hardware in the device's init() function.
> >
> > If somebody wants to subvert the 'design philosophy', the right way is
> > to call eth_dev->init() in board code.
>
> Maybe this list should go in a doc?
the 1. - 4. is already in the documents ive mentioned multiple times, but they
arent short & to the point like Ben has summarized, so that would probably be
good to add as a summary and/or intro to one of them.
Ben's suggestion on how to "subvert" things by forcibly calling eth_dev-
>init() sits best in my book for people insisting on throwing in a hack today.
it could even be done today in the board-specific board_eth_init() function by
calling eth_init() after all the NICs have been registered.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100331/d520b6e8/attachment.pgp
next prev parent reply other threads:[~2010-03-31 6:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 17:46 [U-Boot] [PATCH 1/2 v2] net, fec_mxc: only setup the device enetaddr with eeprom value, if ethaddr is not setup Heiko Schocher
2010-03-30 20:34 ` Wolfgang Denk
2010-03-30 21:57 ` Ben Warren
2010-03-30 21:59 ` Mike Frysinger
2010-03-30 22:16 ` Ben Warren
2010-03-31 5:56 ` Heiko Schocher
2010-03-31 6:07 ` Mike Frysinger [this message]
2010-03-31 6:34 ` [U-Boot] [PATCH 1/2 v3] net, fec_mxc: only setup the device enetaddr with eeprom value Heiko Schocher
2010-03-31 6:50 ` Ben Warren
2010-03-31 8:34 ` Wolfgang Denk
2010-03-31 8:41 ` Wolfgang Denk
2010-05-03 2:38 ` [U-Boot] Toggling pins using the BDI3000 Can Aydin
2010-03-31 6:34 ` [U-Boot] [PATCH] net, doc: how to setup mac address correct Heiko Schocher
2010-03-31 8:50 ` Wolfgang Denk
2010-03-31 13:44 ` [U-Boot] [PATCH 1/2 v2] net, fec_mxc: only setup the device enetaddr with eeprom value, if ethaddr is not setup Detlev Zundel
2010-03-31 13:58 ` Ben Warren
2010-03-31 14:46 ` Detlev Zundel
2010-03-31 19:59 ` Mike Frysinger
2010-03-31 20:04 ` Ben Warren
2010-03-31 9:18 ` Mike Frysinger
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=201003310207.56010.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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