linux-kernel - Re: [linux-usb-devel] [PATCH] : Allow embedded developers USB options normally reserved for OTG

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:	Wed, 2 Jan 2008 14:46:56 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Mike Frysinger <vapier.adi@...il.com>
cc:	David Brownell <david-b@...bell.net>, <gregkh@...e.de>,
	<linux-usb-devel@...ts.sourceforge.net>,
	Robin Getz <rgetz@...ckfin.uclinux.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [linux-usb-devel] [PATCH] : Allow embedded developers USB options
 normally reserved for OTG

On Wed, 2 Jan 2008, Mike Frysinger wrote:

> perhaps the code size is arguable as to whether it really matters.
> the reason we want it is that we have a USB host controller that will
> not work with USB hubs, so we want to make sure the system does not
> attempt such things.  (yes, such a USB host controller is retarded,
> but the decision was out of our hands.)

Just out of curiosity, how does a host controller manage to avoid
working with external hubs?  Is it a matter of power consumption?  It
seems to me that in all other respects a hub should appear the same as
any other USB device.

Or is it a question of whether the controller works when communicating 
with devices behind an external hub?  And if it is, what is the 
difficulty?

Alan Stern

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