From: Josua Dietze <digidietze@draisberghof.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Michał Nazarewicz" <m.nazarewicz@samsung.com>,
"Daniel Mack" <daniel@caiaq.de>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Kernel development list" <linux-kernel@vger.kernel.org>,
"USB list" <linux-usb@vger.kernel.org>,
"Kyungmin Park" <kyungmin.park@samsung.com>
Subject: Re: USB gadget with drivers "on board"
Date: Mon, 26 Apr 2010 22:14:54 +0200 [thread overview]
Message-ID: <4BD5F43E.4090404@draisberghof.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1004261531480.1764-100000@iolanthe.rowland.org>
Alan Stern schrieb:
> On Mon, 26 Apr 2010, Josua Dietze wrote:
>> These are the notorious mode switching devices. In Windows, they
>> obviously install a special storage driver doing one specific action
>> on each following plugging.
>> This action - some storage or control command - will "flip" the
>> device, making it "disconnect" and returning as a completely different
>> composite device.
>>
>> Storage commands used for this procedure range from "SCSI rezero" over
>> "passthrough" to "SCSI eject", or involve vendor specific stuff.
>
> I was going to say the same thing. For ease of use, I recommend using
> a "SCSI eject" to trigger the mode change. That way, Linux users who
> don't have the usb-modeswitch program installed can get the same effect
> by running eject.
Important for the Linux handling is that "mode 1" is clearly
distinguishable from "mode 2", either by using a different product ID
or by setting a different class for the device or interface 0 (will
most likely be "8" for the install mode).
And it might be a good idea not to re-use any known ID for the install
mode, like the 05c6:1000 which my Samsung phone and loads of other
devices are using.
This makes switch handling complicated (though not impossible).
Josua Dietze
next prev parent reply other threads:[~2010-04-26 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 8:29 USB gadget with drivers "on board" Michał Nazarewicz
2010-04-26 14:16 ` Daniel Mack
2010-04-26 14:42 ` Michał Nazarewicz
2010-04-26 14:57 ` Daniel Mack
2010-04-26 15:45 ` Michał Nazarewicz
2010-04-26 17:37 ` Josua Dietze
2010-04-26 19:34 ` Alan Stern
2010-04-26 20:14 ` Josua Dietze [this message]
2010-04-28 8:46 ` Michał Nazarewicz
2010-04-28 11:31 ` Michał Nazarewicz
2010-04-28 11:41 ` Josua Dietze
2010-04-28 11:54 ` Michał Nazarewicz
2010-04-28 15:59 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BD5F43E.4090404@draisberghof.de \
--to=digidietze@draisberghof.de \
--cc=daniel@caiaq.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.nazarewicz@samsung.com \
--cc=m.szyprowski@samsung.com \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox