From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] Program net device MAC addresses after initializing
Date: Mon, 26 Apr 2010 09:35:07 -0700 [thread overview]
Message-ID: <4BD5C0BB.4040403@gmail.com> (raw)
In-Reply-To: <20100426115216.C8414C1584A@gemini.denx.de>
Hi Wolfgang,
On 4/26/2010 4:52 AM, Wolfgang Denk wrote:
> Dear Ben Warren,
>
> In message<1272261030-9419-1-git-send-email-biggerbadderben@gmail.com> you wrote:
>
>> Add a new function to the eth_device struct for programming a network
>> controller's hardware address.
>>
>> After all network devices have been initialized and the proper MAC address for
>> each has been determined, make a device driver call to program the address
>> into the device. Only device instances with valid unicast addresses will be
>> programmed.
>>
> Thanks.
>
>
>> +If Ethernet drivers implement the 'write_hwaddr' function, valid MAC addresses
>> +will be programmed into hardware as part of the initialization process. This
>> +may be skipped by setting the appropriate 'ethmacskip' environment variable.
>> +The naming convention is as follows:
>> +"eth0macskip" (=>eth0), "eth1macskip" (=>eth1) etc.
>>
> Would it not be more consistent to use "ethmacskip" instead of
> "eth0macskip" similar to using "ethaddr" (instead of "eth0addr") ?
>
>
I guess it depends which consistency we're going for :) We can be
consistent relative to an existing variable that is itself inconsistent
for historical reasons, or we can be consistent in usage of the new
variable. I don't have a strong opinion either way, so will change this.
> The majority of boards still has only a single Ethernet interface
> anyway.
>
> Best regards,
>
> Wolfgang Denk
>
>
regards,
Ben
prev parent reply other threads:[~2010-04-26 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 5:50 [U-Boot] [PATCH v2] Program net device MAC addresses after initializing Ben Warren
2010-04-26 11:52 ` Wolfgang Denk
2010-04-26 12:03 ` Prafulla Wadaskar
2010-04-26 16:35 ` Ben Warren [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=4BD5C0BB.4040403@gmail.com \
--to=biggerbadderben@gmail.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