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]

Date:	Fri, 18 Mar 2011 10:42:23 +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 12:11 AM, ext Arnd Bergmann wrote:
> On Thursday 17 March 2011 21:26:14 Greg KH wrote:
>>> It's going to be an off the shelf USB ethernet controller.  I'd be
>>> astonished if the board-configurable device IDs weren't set from the
>>> same SEPROM that the MAC address is so it'd just show up as a generic
>>> chip of whatever kind.
>>
>> Huh?  All USB controllers you buy have the ability to set the vendor and
>> product id, so you should always be able to key off of that.
>>
>> Isn't that the case here?
> 
> The same EEPROM that is missing here carries both the MAC address and
> the vendor/product ID overrides.
> 

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?

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