public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] Program net device MAC addresses after	initializing
Date: Tue, 27 Apr 2010 07:41:32 +0200	[thread overview]
Message-ID: <4BD6790C.2090601@denx.de> (raw)
In-Reply-To: <1272306230-20453-1-git-send-email-biggerbadderben@gmail.com>

Hello Ben,

Ben Warren 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.
> 
> Signed-off-by: Ben Warren <biggerbadderben@gmail.com>
> Acked-by: Heiko Schocher <hs@denx.de>
> Acked-by: Detlev Zundel <dzu@denx.de>
> Tested-by: Prafulla Wadaskar <prafulla@marvell.com>
> ---
> v4->v3 First controller uses 'ethmacskip' instead of 'eth0macskip'
> v2->v3 Made the sprintf in new function actually work :(
> v1->v2 Add documentation & environment variable for overriding new behavior
> ACKs mentioned above are for v1
> 
>  README                 |    5 +++++
>  doc/README.drivers.eth |    7 ++++++-
>  doc/README.enetaddr    |   10 ++++++----
>  include/net.h          |    1 +
>  net/eth.c              |   13 +++++++++++++
>  5 files changed, 31 insertions(+), 5 deletions(-)

Tested on the magnesium board, patch for adapting fec_mxc
driver follow, so:

Tested-by: Heiko Schocher <hs@denx.de>

bye
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2010-04-27  5:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 18:23 [U-Boot] [PATCH v4] Program net device MAC addresses after initializing Ben Warren
2010-04-27  5:41 ` Heiko Schocher [this message]
2010-04-27  6:15 ` Thomas Chou
2010-04-27 17:01 ` Ben Warren

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=4BD6790C.2090601@denx.de \
    --to=hs@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