In order to support an older USB cradle by Denso, I added its vendor- and
product-ID to the array of usb_device_id acm_ids. In this way cdc-acm feels
responsible for this cradle. The related /dev/ttyACM node is being created
properly, and the data transfer works.
However, later cradle models
Greg KH g...@kroah.com hat am 17. Februar 2015 um 15:55 geschrieben:
On Tue, Feb 17, 2015 at 01:10:40PM +0100, Björn Gerhart wrote:
Hello,
in order to support an older USB cradle by Denso, I added its
vendor-
and product-ID to the array of usb_device_id acm_ids. In this way
cdc
In order to support an older USB cradle by Denso, I added its vendor-
and product-ID to the array of usb_device_id acm_ids. In this way
cdc-acm feels responsible for this cradle. The related /dev/ttyACM node
is being created properly, and the data transfer works.
However, later cradle models by
Hello,
in order to support an older USB cradle by Denso, I added its vendor-
and product-ID to the array of usb_device_id acm_ids. In this way
cdc-acm feels responsible for this cradle. The related /dev/ttyACM
node is being created properly, and the data transfer works.
However, later cradle
