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: <20110311165325.GU1760@opensource.wolfsonmicro.com>
Date:	Fri, 11 Mar 2011 16:53:26 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	andy.green@...aro.org, Arnd Bergmann <arnd@...db.de>,
	Linux USB list <linux-usb@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: RFC: Platform data for onboard USB assets

On Fri, Mar 11, 2011 at 11:45:20AM -0500, Alan Stern wrote:

> Or to put it another way...  With external, hot-plugged USB devices,
> there is no need to know "how it is wired".  The fact that it is on a 
> USB bus is the only information necessary.  Why does anyone need to
> know more than this for on-board USB devices?

Examples I'm aware of include things like power control beyond what the
USB spec does and not programming device identification or configuration
information that would normally be initialised by the hardware, relying
on the AP to program it at runtime.
--
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/