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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 28 Feb 2012 13:11:06 -0000
From:	"David Laight" <David.Laight@...LAB.COM>
To:	"Roland Stigge" <stigge@...com.de>, <baruch@...s.co.il>
Cc:	<alexander.h.duyck@...el.com>, <ian.campbell@...rix.com>,
	<netdev@...r.kernel.org>, <eilong@...adcom.com>,
	"Kevin Wells" <kevin.wells@....com>,
	"Wolfram Sang" <w.sang@...gutronix.de>,
	<jeffrey.t.kirsher@...el.com>, <linux-kernel@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH v2] ARM: LPC32xx: Ethernet driver

 
> Thanks for the note! I actually found out that in many cases, the
> bootloader already initialized the hardware with the target 
> MAC address so we can use this one.
> 
> 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.)

Using a fixed address is a very bad idea ...

	David


--
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

Powered by blists - more mailing lists