From: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
To: digidietze@draisberghof.de
Cc: Alan Stern <stern@rowland.harvard.edu>,
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: Wed, 28 Apr 2010 13:54:17 +0200 [thread overview]
Message-ID: <op.vbvfcrps7p4s8u@pikus> (raw)
In-Reply-To: <4BD81ED5.1050408@draisberghof.de>
> Michał Nazarewicz schrieb:
>> 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.
On Wed, 28 Apr 2010 13:41:09 +0200, Josua Dietze <digidietze@draisberghof.de> wrote:
> That is up to the (countless) manufacturers of course; on the
> other hand, the Windows drivers need to recognize the mode as
> well so there should always be one way or the other to
> accomplish that.
Windows most likely recognises the device by vendor and product ID after the
drivers are installed. On Linux you add a rule to udev (if I understand
correctly) which is a bit of a burden because (i) it takes time and (ii) the
list must be updated. What I'm thinking is creating a generic way of marking
"install mode" devices so that no such list is necessary. Of course, it'll
take time for vendors to recognise this scheme but maybe over time some major
players will.
--
Best regards, _ _
| Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o
| Computer Science, Michał "mina86" Nazarewicz (o o)
+----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo--
next prev parent reply other threads:[~2010-04-28 11:54 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
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 [this message]
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=op.vbvfcrps7p4s8u@pikus \
--to=m.nazarewicz@samsung.com \
--cc=daniel@caiaq.de \
--cc=digidietze@draisberghof.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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