netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: stigge@antcom.de
Cc: alexander.h.duyck@intel.com, baruch@tkos.co.il,
	ian.campbell@citrix.com, netdev@vger.kernel.org,
	eilong@broadcom.com, kevin.wells@nxp.com, w.sang@pengutronix.de,
	jeffrey.t.kirsher@intel.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ARM: LPC32xx: Ethernet driver
Date: Tue, 28 Feb 2012 14:13:34 -0500 (EST)	[thread overview]
Message-ID: <20120228.141334.569125676685228205.davem@davemloft.net> (raw)
In-Reply-To: <4F4CD1D8.8030102@antcom.de>

From: Roland Stigge <stigge@antcom.de>
Date: Tue, 28 Feb 2012 14:08:40 +0100

> For the case that it _isn't_ initialized already, is it the right thing
> to use a hard coded default MAC address to be replaced by the final one
> in userspace? (I found such examples in some current micrel/ and amd/
> drivers.)

You use a randomized ethernet address which can subsequently be fixed up
by userspace, and we have very specific interfaces to make this very
easy for you.  It even sets an attribute which userland can query to see
that the device has a randomized ethernet address rathern than a true
assigned permanent one.

  parent reply	other threads:[~2012-02-28 19:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 13:08 [PATCH v2] ARM: LPC32xx: Ethernet driver Roland Stigge
2012-02-28 13:11 ` David Laight
2012-02-28 13:32   ` Roland Stigge
2012-02-28 13:41     ` Arnd Bergmann
2012-02-28 13:49       ` Roland Stigge
2012-02-28 15:53       ` Ben Hutchings
2012-02-28 19:13 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-25 20:21 Roland Stigge
2012-02-25 20:41 ` Joe Perches
2012-02-26  1:52 ` Baruch Siach
2012-02-26  2:28   ` David Miller

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=20120228.141334.569125676685228205.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexander.h.duyck@intel.com \
    --cc=baruch@tkos.co.il \
    --cc=eilong@broadcom.com \
    --cc=ian.campbell@citrix.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=kevin.wells@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stigge@antcom.de \
    --cc=w.sang@pengutronix.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;
as well as URLs for NNTP newsgroup(s).