From: Ben Hutchings <bhutchings@solarflare.com>
To: "Richard Röjfors" <richard.rojfors@pelagicore.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] ks8842: Add module param for setting mac address
Date: Sun, 18 Apr 2010 20:50:21 +0100 [thread overview]
Message-ID: <1271620221.3679.265.camel@localhost> (raw)
In-Reply-To: <1271611557.24099.11.camel@debian>
On Sun, 2010-04-18 at 19:25 +0200, Richard Röjfors wrote:
> This patch adds a module parameter for setting the MAC address.
>
> To ensure this MAC address is used, the MAC address is written
> after each hardware reset.
[...]
This is not an accepted way of setting the MAC address. The accepted
ways to initialise a network controller's address are:
1. a. Controller reads it from dedicated NVRAM. Driver reads it from
controller.
b. Driver reads it from dedicated NVRAM.
2. Platform firmware or boot loader passes platform data (OpenFirmware,
device tree, etc.) to the kernel, which includes the assigned MAC
address. Driver uses kernel functions to read it from platform data.
3. Platform firmware or boot loader programs it into the controller.
Driver reads it from the controller.
4. Driver generates random address.
In any case, userland can change the MAC address later.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-04-18 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 17:25 [PATCH] ks8842: Add module param for setting mac address Richard Röjfors
2010-04-18 19:50 ` Ben Hutchings [this message]
2010-04-18 21:35 ` Richard Röjfors
2010-04-19 4:18 ` David Miller
2010-04-19 6:16 ` Richard Röjfors
2010-04-19 6:36 ` David Miller
2010-04-19 6:46 ` Richard Röjfors
2010-04-19 7:13 ` 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=1271620221.3679.265.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=richard.rojfors@pelagicore.com \
/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).