netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux@fluff.org>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] DM9000: platform dependent fill_ether_addr method
Date: Fri, 18 Apr 2008 16:21:14 +0100	[thread overview]
Message-ID: <20080418152114.GI15407@fluff.org.uk> (raw)
In-Reply-To: <1208512936-5897-1-git-send-email-enrico.scholz@sigma-chemnitz.de>

On Fri, Apr 18, 2008 at 12:02:14PM +0200, Enrico Scholz wrote:
> This patch adds a fill_ether_addr() method to the DM9000 platform data
> which can be used to fill in the MAC address in a platform specific manner
> (e.g. calculate it out of the serial number).
> 
> This method will be called only, when MAC was not set previously (e.g. by
> bootloader) or can be read out of the EEPROM.

I belive this has come up on the list a number of times before, and
the general answer is that either the bootloader is at fault for not
initialising the chip, the manufacturer should have shoved an EEPROM
on for configuration. The general answer is that the driver should not
be making up for the fault of the system.

I'm not sure if you can pass the mac via a commandline argument, that
is something you'll have to research for yourself.
 
> Having a valid MAC address in early bootstage is necessary e.g. for booting
> from network.

No, you can load an initramfs to set the mac via ethtool and then
continue with the boot.
 
-- 
Ben (ben@fluff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'

      reply	other threads:[~2008-04-18 15:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 10:02 [PATCH] DM9000: platform dependent fill_ether_addr method Enrico Scholz
2008-04-18 15:21 ` Ben Dooks [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=20080418152114.GI15407@fluff.org.uk \
    --to=ben-linux@fluff.org \
    --cc=enrico.scholz@sigma-chemnitz.de \
    --cc=netdev@vger.kernel.org \
    /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).