netdev - Re: [PATCH] DM9000: platform dependent fill_ether

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080418152114.GI15407@fluff.org.uk>
Date:	Fri, 18 Apr 2008 16:21:14 +0100
From:	Ben Dooks <ben-linux@...ff.org>
To:	Enrico Scholz <enrico.scholz@...ma-chemnitz.de>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] DM9000: platform dependent fill_ether_addr method

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@...ff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html