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: <20110317222020.GA30486@kroah.com>
Date:	Thu, 17 Mar 2011 15:20:20 -0700
From:	Greg KH <greg@...ah.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	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 Thu, Mar 17, 2011 at 11:11:36PM +0100, 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.

{sigh}

It's as if BIOS programmers are now laying out board designs...
--
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/