From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mvgbe: remove setting of ethaddr within the driver
Date: Tue, 8 Nov 2011 18:34:17 +0100 [thread overview]
Message-ID: <45fd92b472c944e2cb9ebb409488ccfc.squirrel@ssl.serverraum.org> (raw)
In-Reply-To: <20111108151736.1352C13BE0C5@gemini.denx.de>
Hi Wolfgang, Hi Mike,
Am Di, 8.11.2011, 16:17 schrieb Wolfgang Denk:
> Dear "Michael Walle",
>
> In message <89e599b8867346f857ae2f132e9717a3.squirrel@ssl.serverraum.org>
> you wrote:
>>
>> >> +#define CONFIG_ETH_ADDR 02:50:43:00:00:01
>> >
>> > NAK to this. board configs are not allow to hardcode MACs.
>> mh, so why is there a CONFIG_ETH_ADDR macro? is it deprecated?
>> README.enetaddr explicitly refers to that config option.
>
> There are situations where it cannot be helped, like when programming
> the U-Boot image into a ROM (yes, a real ROM that cannot be changed
> any more by software alone).
>
> But in almost all normal situations this must not be used. In any
> case, we will not accept it into mainline.
I have a Buffalo Linkstation Pro LS-XHL for which i plan to submit a BSP.
On this board, the MAC address is saved within the environment, which is
in turn stored in flash. Additionally this board does not have a serial
port, thus the only available console is the network console.
If someone will mess up the environment, it is possible to clear it by
holding a button upon powerup. Atm i have the CONFIG_ETH_ADDR set to a
default MAC address to be able to use the network console with the default
environment. To restore the original MAC address, a user have to manually
replace ethaddr with the one printed on the case.
But now, if i can't use the CONFIG_ETH_ADDR, i think i'm stuck :) Or do i
miss something? (Yeah there may be the MAC randomization, if accepted).
--
Michael
next prev parent reply other threads:[~2011-11-08 17:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 22:08 [U-Boot] [PATCH] mvgbe: remove setting of ethaddr within the driver Michael Walle
2011-11-08 7:18 ` Prafulla Wadaskar
2011-11-08 13:58 ` Mike Frysinger
2011-11-08 14:10 ` Wolfgang Denk
2011-11-08 13:57 ` Mike Frysinger
2011-11-08 13:45 ` Michael Walle
2011-11-08 14:54 ` Mike Frysinger
2011-11-08 15:17 ` Wolfgang Denk
2011-11-08 17:34 ` Michael Walle [this message]
2011-11-08 19:28 ` Wolfgang Denk
2011-11-08 22:30 ` Michael Walle
2011-11-08 22:52 ` Wolfgang Denk
2011-11-08 23:26 ` Michael Walle
2011-11-08 23:38 ` Wolfgang Denk
2011-11-09 8:31 ` Michael Walle
2011-11-09 17:34 ` Michael Walle
2011-11-09 19:27 ` Wolfgang Denk
2011-11-10 9:15 ` Michael Walle
2011-11-10 11:06 ` Simon Guinot
2011-11-10 12:01 ` Wolfgang Denk
2011-11-10 14:21 ` Simon Guinot
2011-11-10 15:53 ` Wolfgang Denk
2011-11-10 16:30 ` Valentin Longchamp
2011-11-10 17:00 ` Holger Brunck
2011-11-10 17:08 ` Mike Frysinger
2011-11-10 17:09 ` Mike Frysinger
2011-11-10 17:54 ` Simon Guinot
2011-11-10 17:46 ` Michael Walle
2011-11-10 11:44 ` Wolfgang Denk
2011-11-16 20:15 ` Michael Walle
2011-11-16 20:26 ` Wolfgang Denk
2011-11-17 8:58 ` Prafulla Wadaskar
2011-11-17 10:45 ` Wolfgang Denk
2011-11-17 22:52 ` [U-Boot] [PATCH v2] " Michael Walle
2011-11-19 3:58 ` Mike Frysinger
2011-11-21 4:39 ` Prafulla Wadaskar
2011-12-20 21:55 ` Wolfgang Denk
2011-12-20 21:57 ` Wolfgang Denk
2011-11-08 20:49 ` [U-Boot] [PATCH] " Mike Frysinger
2011-11-08 22:45 ` Michael Walle
2011-11-09 5:36 ` 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=45fd92b472c944e2cb9ebb409488ccfc.squirrel@ssl.serverraum.org \
--to=michael@walle.cc \
--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