From: Praveena NADAHALLY <praveen.nadahally@xxxxxxxxxxxxxx>
Why the protocol code is set 00 in IAD and it's set
to 01 in ACM control interface descriptor in f_acm.c file?
Shouldn't IAD be the same as in ACM control interface
descriptor?
At the moment I don't really remember why I've put USB_CDC_PROTO_NONE there.
Still, <http://msdn.microsoft.com/en-us/library/ff537109(v=VS.85).aspx> doesn't
require IAD's bFunctionProtocol to be set. Interestingly enough, an example
from the page does not follow recommendation stated earlier on the very same
page.
If setting bFunctionProtocol to USB_CDC_ACM_PROTO_AT_V25TER helps, I thing you
should go for it.
On Thu, 02 Sep 2010 00:32:51 +0200, David Brownell <david-b@xxxxxxxxxxx> wrote:
Seems buglike to me. Almost as buglike as even
wanting an IAD given a CDC Union descriptor.
Windows failed to correctly detect composite functions in a composite
gadget if IAD's were missing.
Ideally, a patch that adds IAD only for composite gadget (ie. gadget with
many composite functions) would be perfect.
--
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--
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
