Re: USB CDC ACM -- why is bProtocol required to be nonzero?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 11 Dec 2009 13:04:48 +0100 Simon Richter
<Simon.Richter@xxxxxxxxxx> wrote:
> Hi,
> 
> I'm building an USB to serial converter which implements CDC
> ACM.

Hm, seems like we are doing the same. How are you implementing
it? I am doing it in an FPGA with VHDL. Maybe we can work
together. I was planning on setting up a git repo of the VHDL
code somewhere under a GPL license. The basic version is
already working, but has some bugs. Let me know what you think,
maybe by personal mail.

> Since I do not know what kind of device is connected to
> the serial port, I cannot list a protocol value in the
> bInterfaceProtocol field; however if I set it to zero, the
> cdc-acm driver ignores my device, because there is no entry in
> the table for this.

For the data interface I use 0x00, for the notify interface 0x01.
But you need to set the vendor id to something else than 0xffff.

> 
> From what I can see, adding such an entry would be nontrivial,
> as a zero in this table is effectively regarded as a wildcard.
> 
> I can work around it for now by claiming my device is connected
> to a modem, but would rather have a technically sound solution.

That would be nice, indeed.

> 
> Any ideas?
> 
>    Simon

~Henry
--
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

[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux