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

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

 



Hi,

I'm building an USB to serial converter which implements CDC ACM. 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.

>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.

Any ideas?

   Simon
--
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