linux-kernel - Re: USB gadget with drivers "on board"

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

Message-ID: <Pine.LNX.4.44L0.1004281156100.1944-100000@iolanthe.rowland.org>
Date:	Wed, 28 Apr 2010 11:59:04 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Michał Nazarewicz <m.nazarewicz@...sung.com>
cc:	Josua Dietze <digidietze@...isberghof.de>,
	Daniel Mack <daniel@...aq.de>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB list <linux-usb@...r.kernel.org>,
	Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: USB gadget with drivers "on board"

On Wed, 28 Apr 2010, [utf-8] MichaÅ Nazarewicz wrote:

> So it will be enough to change the USB device class for the zeroth
> interface for udev to recognise the mass storage to be ejected?  Note
> that I will use mass storage in the second mode as well.

No, you also have to go through a disconnect-reconnect cycle on the USB 
bus.  When you do, changing the bInterfaceClass value will be 
sufficient to tell the kernel that the device needs to be 
re-enumerated.

> Also, I think that it might be a good idea to make some "standardised"
> mechanism for all such devices so that a generic udev code could be
> written.  Adding things to the descriptors may be difficult in a way,
> but maybe adding "[NoCD]" to the interface name would be enough.

I seriously doubt you'll be able to convince all the other
manufacturers to agree to a standardized convention for this.

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/