Re: Adding new usbserial device

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

 



On Tue, Jul 11, 2017 at 01:32:00PM +0300, Anton Avramov wrote:
> Hello, 
> 
> I have a new device in my possession that works with usbserial generic
> driver. 
> In order for it to work I execute: 
> modprobe usbserial
> echo fff0 0100 > /sys/bus/usb-serial/drivers/generic/new_id 
> 
> I'm writing to you since dmesg reads: 
> [ 1674.626941] usbserial_generic 4-2:1.0: Generic device with no bulk
> out, not allowed.
> [ 1674.626972] usbserial_generic: probe of 4-2:1.0 failed with error -5
> [ 1674.626991] usbserial_generic 4-2:1.1: The "generic" usb-serial
> driver is only for testing and one-off prototypes.
> [ 1674.626997] usbserial_generic 4-2:1.1: Tell linux-usb@xxxxxxxxxxxxxx
> g to add your device to a proper driver.
> [ 1674.627002] usbserial_generic 4-2:1.1: generic converter detected
> [ 1674.627276] usb 4-2: generic converter now attached to ttyUSB0

Thanks for reporting this to us.

> query the device pins: 
> 
> /usr/bin/statserial -d /dev/ttyUSB0
> statserial: TIOCMGET failed: Invalid argument

Yeah, that's not expected to work with the generic driver.

>   looking at parent device '/devices/pci0000:00/0000:00:04.0/usb4/4-
> 2/4-2:1.1':
>     KERNELS=="4-2:1.1"
>     SUBSYSTEMS=="usb"
>     DRIVERS=="usbserial_generic"
>     ATTRS{bInterfaceClass}=="0a"
>     ATTRS{bInterfaceSubClass}=="00"
>     ATTRS{bInterfaceProtocol}=="00"
>     ATTRS{bNumEndpoints}=="02"
>     ATTRS{supports_autosuspend}=="1"
>     ATTRS{bAlternateSetting}==" 0"
>     ATTRS{bInterfaceNumber}=="01"
> 
>   looking at parent device '/devices/pci0000:00/0000:00:04.0/usb4/4-2':
>     KERNELS=="4-2"
>     SUBSYSTEMS=="usb"
>     DRIVERS=="usb"
>     ATTRS{bDeviceSubClass}=="00"
>     ATTRS{bDeviceProtocol}=="00"
>     ATTRS{devpath}=="2"
>     ATTRS{idVendor}=="fff0"
>     ATTRS{speed}=="12"
>     ATTRS{bNumInterfaces}==" 2"
>     ATTRS{bConfigurationValue}=="1"
>     ATTRS{bMaxPacketSize0}=="64"
>     ATTRS{busnum}=="4"
>     ATTRS{devnum}=="2"
>     ATTRS{configuration}==""
>     ATTRS{bMaxPower}=="0mA"
>     ATTRS{authorized}=="1"
>     ATTRS{bmAttributes}=="c0"
>     ATTRS{bNumConfigurations}=="1"
>     ATTRS{maxchild}=="0"
>     ATTRS{bcdDevice}=="0100"
>     ATTRS{avoid_reset_quirk}=="0"
>     ATTRS{quirks}=="0x0"
>     ATTRS{serial}=="DT653794"
>     ATTRS{version}==" 1.01"
>     ATTRS{urbnum}=="42"
>     ATTRS{ltm_capable}=="no"
>     ATTRS{manufacturer}=="DATECS"
>     ATTRS{removable}=="unknown"
>     ATTRS{idProduct}=="0100"
>     ATTRS{bDeviceClass}=="02"
>     ATTRS{product}=="Fiscal Printer FP-2000"

This looks like you should be using the cdc-acm driver instead, but
please provide the output of "lsusb -v" for this device first (as that
is a bit easier to parse).

Thanks,
Johan
--
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