mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Nazarewicz <mina86@mina86.com>
To: Xiaofan Chen <xiaofanc@gmail.com>
Cc: "Dries Van Puymbroeck" <dries.van.puymbroeck@gmail.com>,
	linux-usb@vger.kernel.org, "Greg KH" <greg@kroah.com>,
	"Michał Nazarewicz" <m.nazarewicz@samsung.com>,
	"Dries Van Puymbroeck" <dries.vanpuymbroeck@dekimo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: Gadget: g_multi: added INF file for gadget with multiple configurations
Date: Sat, 14 Aug 2010 10:39:06 +0200	[thread overview]
Message-ID: <87r5i1h9lh.fsf@erwin.mina86.com> (raw)
In-Reply-To: <AANLkTin_o36qmavka+aJaDOBpNRGc=xxKdPdtWWUcVG8@mail.gmail.com> (Xiaofan Chen's message of "Sat, 14 Aug 2010 09:27:57 +0800")

Xiaofan Chen <xiaofanc@gmail.com> writes:
> Basically I am just wondering if the following statement is true or not.

> On Fri, Aug 13, 2010 at 5:31 PM, Dries Van Puymbroeck wrote:
>> When a mutlifunction gadget has more than 1 configuration, Windows does not
>> use its generic driver for multifunction USB devices.

> I am thinking the inf file is not necessary.
> "When the system detects that a USB device is composite, it loads the
> USB common class generic parent driver (usbccgp.sys)."
> http://msdn.microsoft.com/en-us/library/ff538059%28VS.85%29.aspx

<http://msdn.microsoft.com/en-us/library/ff537109(v=VS.85).aspx>
specifies that for a device to be identified as composite it (among
other things) "must have a single configuration".  The page has also
a passage which seems to indicate that the INF is needed:

> If you want the generic parent driver to manage your device, but your
> device does not have the characteristics necessary to ensure that the
> system will generate a compatible ID of USB\COMPOSITE, you will have
> to provide an INF file that loads the generic parent driver.

Selecting of the configuration is also mentioned as a requirement, and
the next paragraph points to a web page you've cited:

> If your composite device has multiple configurations, the INF file you
> provide must specify which configuration the generic parent should use
> in the registry. The necessary registry keys are described in
> Selecting the Configuration for a Composite USB Device.

-- 
Best regards,                                         _     _
 .o. | Liege of Serenly Enlightened Majesty of      o' \,=./ `o
 ..o | Computer Science,  Michal "mina86" Nazarewicz   (o o)
 ooo +--<mina86-tlen.pl>--<jid:mina86-jabber.org>--ooO--(_)--Ooo--

  reply	other threads:[~2010-08-14  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13  9:31 Dries Van Puymbroeck
2010-08-13 13:31 ` Xiaofan Chen
2010-08-13 20:35   ` Michal Nazarewicz
2010-08-14  1:27     ` Xiaofan Chen
2010-08-14  8:39       ` Michal Nazarewicz [this message]
2010-08-14  8:57         ` Xiaofan Chen
2010-08-16  8:07           ` Dries Van Puymbroeck

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=87r5i1h9lh.fsf@erwin.mina86.com \
    --to=mina86@mina86.com \
    --cc=dries.van.puymbroeck@gmail.com \
    --cc=dries.vanpuymbroeck@dekimo.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.nazarewicz@samsung.com \
    --cc=xiaofanc@gmail.com \
    /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

Powered by JetHome