linux-kernel - Re: RFC: Platform data for onboard USB assets

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D832BF4.9000004@nokia.com>
Date:	Fri, 18 Mar 2011 11:55:00 +0200
From:	Roger Quadros <roger.quadros@...ia.com>
To:	ext Arnd Bergmann <arnd@...db.de>
CC:	Greg KH <greg@...ah.com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Nicolas Pitre <nicolas.pitre@...aro.org>,
	<andy.green@...aro.org>,
	Linux USB list <linux-usb@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: RFC: Platform data for onboard USB assets

On 03/18/2011 11:01 AM, ext Arnd Bergmann wrote:
> On Friday 18 March 2011, Roger Quadros wrote:
>> Just curious, how do Panda boards manage to get the MAC address? Is it
>> programmed in some other flash memory?
>>
>> The LAN9514 datasheet says
>> "If a properly configured EEPROM is not detected, it is the
>> responsibility of the Host LAN Driver to set the IEEE addresses."
>>
>> So how does the Host LAN driver know what MAC address it should use?
> 
> This is the problem we're trying to work out. The EEPROM is not
> present, and user space has no way of knowing which MAC address
> to set to which device. Note that there might be multiple
> USB devices of the same type that are indistinguishable to user
> space, so setting the MAC address there would not be completely
> safe.
> 

And what happens if you need to use u-boot or some bootloader with
ethernet network support?

Wouldn't it be better to have the MAC address programmed at the
bootloader level?

-- 
regards,
-roger
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/