[ Please avoid top posting, and don't drop recipients from CC
(resending). ]
Adding Oliver on CC and keeping the context.
On Thu, Apr 13, 2017 at 11:06:41AM +0200, Ralf Hartmann wrote:
> and the other:
>
> dmesg:
>
> [ 2043.668380] usb 4-1: USB disconnect, device number 4
> [ 2043.669589] generic ttyUSB2: generic converter now disconnected from
> ttyUSB2
> [ 2043.669611] usbserial_generic 4-1:1.1: device disconnected
> [ 2048.120022] usb 4-1: new full-speed USB device number 5 using uhci_hcd
> [ 2048.304077] usb 4-1: New USB device found, idVendor=09d8, idProduct=0320
> [ 2048.304089] usb 4-1: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [ 2048.304097] usb 4-1: Product: RFID Device (COM)
> [ 2048.304104] usb 4-1: Manufacturer: OEM
>
> lsusb:
>
> Bus 004 Device 005: ID 09d8:0320
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 2 Communications
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 8
> idVendor 0x09d8
> idProduct 0x0320
> bcdDevice 3.00
> iManufacturer 1 OEM
> iProduct 2 RFID Device (COM)
> iSerial 0
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 67
> bNumInterfaces 2
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0x80
> (Bus Powered)
> MaxPower 250mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 1
> bInterfaceClass 2 Communications
> bInterfaceSubClass 2 Abstract (modem)
> bInterfaceProtocol 1 AT-commands (v.25ter)
This looks like you should be using the cdc-acm driver and that it
should work out of the box. Have you enabled that driver? Or does it
fail to bind for some reason?
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x83 EP 3 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0020 1x 32 bytes
> bInterval 2
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 1
> bAlternateSetting 0
> bNumEndpoints 2
> bInterfaceClass 10 CDC Data
> bInterfaceSubClass 0 Unused
> bInterfaceProtocol 0
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x02 EP 2 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0020 1x 32 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0020 1x 32 bytes
> bInterval 0
> CDC Header:
> bcdCDC 1.10
> CDC Call Management:
> bmCapabilities 0x03
> call management
> use DataInterface
> bDataInterface 1
> CDC ACM:
> bmCapabilities 0x06
> sends break
> line coding and serial state
> CDC Union:
> bMasterInterface 0
> bSlaveInterface 1
> Device Status: 0x0000
> (Bus Powered)
> Am 13.04.2017 um 10:59 schrieb Johan Hovold:
> > On Thu, Apr 13, 2017 at 10:50:59AM +0200, Ralf Hartmann wrote:
> >> '09d8 0320' and '09d8 0420' ('vendor' 'product') are serial devices.
> >> This are TWN3 and TWN4 RFID-CardREaders from elatec GmbH.
> >>
> >> They work fine with the generic driver.
> > Thanks for the report.
> >
> >> Here the output of dmesg (TWN4 connected)
> >>
> >> [ 837.228021] usb 4-1: new full-speed USB device number 4 using uhci_hcd
> >> [ 837.409161] usb 4-1: New USB device found, idVendor=09d8, idProduct=0420
> >> [ 837.409165] usb 4-1: New USB device strings: Mfr=1, Product=2,
> >> SerialNumber=0
> >> [ 837.409168] usb 4-1: Product: RFID Device (CDC)
> >> [ 837.409169] usb 4-1: Manufacturer: OEM
> >> [ 837.413225] usbserial_generic 4-1:1.0: Generic device with no bulk
> >> out, not allowed.
> >> [ 837.413234] usbserial_generic: probe of 4-1:1.0 failed with error -5
> >> [ 837.413293] usbserial_generic 4-1:1.1: The "generic" usb-serial
> >> driver is only for testing and one-off prototypes.
> >> [ 837.413295] usbserial_generic 4-1:1.1: Tell [email protected]
> >> to add your device to a proper driver.
> >> [ 837.413297] usbserial_generic 4-1:1.1: generic converter detected
> >> [ 837.413369] usb 4-1: generic converter now attached to ttyUSB2
> > But you at least don't want to (attempt to) bind to the first interface
> > it seems.
> >
> > What is the output of "lsusb -v" for these devices?
Thanks,
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
