Re: cdc-acm linux kernel

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

 



I tried to do so, but for some reason I did not answer the serial port?

20.08.2018, 16:46, "Johan Hovold" <johan@xxxxxxxxxx>:
> [ Reshuffling your reply, and responding inline below ]
>
> On Mon, Aug 20, 2018 at 04:27:37PM +0300, Алексей Болдырев wrote:
>>  > 20.08.2018, 11:42, "Johan Hovold" <johan@xxxxxxxxxx>:
>>  >> [ Adding linux-usb on CC. ]
>>  >>
>>  >> On Fri, Aug 17, 2018 at 10:41:20PM +0300, Алексей Болдырев wrote:
>>  >>>  please add support to device from cdc-acm:
>>  >>>
>>  >>>  Bus 004 Device 003: ID 1782:3d00 Spreadtrum Communications Inc.
>>  >>
>>  >> Can you please post the output of "lsusb -v" for this device?
>
>>  Bus 004 Device 004: ID 1782:3d00 Spreadtrum Communications Inc.
>>  Couldn't open device, some information will be missing
>>  Device Descriptor:
>>    bLength 18
>>    bDescriptorType 1
>>    bcdUSB 1.10
>>    bDeviceClass 0 (Defined at Interface level)
>>    bDeviceSubClass 0
>>    bDeviceProtocol 0
>>    bMaxPacketSize0 64
>>    idVendor 0x1782 Spreadtrum Communications Inc.
>>    idProduct 0x3d00
>>    bcdDevice 0.01
>>    iManufacturer 0
>>    iProduct 0
>>    iSerial 0
>>    bNumConfigurations 1
>>    Configuration Descriptor:
>>      bLength 9
>>      bDescriptorType 2
>>      wTotalLength 55
>>      bNumInterfaces 2
>>      bConfigurationValue 1
>>      iConfiguration 0
>>      bmAttributes 0xc0
>>        Self Powered
>>      MaxPower 100mA
>>      Interface Descriptor:
>>        bLength 9
>>        bDescriptorType 4
>>        bInterfaceNumber 0
>>        bAlternateSetting 0
>>        bNumEndpoints 2
>>        bInterfaceClass 255 Vendor Specific Class
>>        bInterfaceSubClass 0
>>        bInterfaceProtocol 0
>>        iInterface 0
>>        Endpoint Descriptor:
>>          bLength 7
>>          bDescriptorType 5
>>          bEndpointAddress 0x81 EP 1 IN
>>          bmAttributes 2
>>            Transfer Type Bulk
>>            Synch Type None
>>            Usage Type Data
>>          wMaxPacketSize 0x0040 1x 64 bytes
>>          bInterval 0
>>        Endpoint Descriptor:
>>          bLength 7
>>          bDescriptorType 5
>>          bEndpointAddress 0x02 EP 2 OUT
>>          bmAttributes 2
>>            Transfer Type Bulk
>>            Synch Type None
>>            Usage Type Data
>>          wMaxPacketSize 0x0040 1x 64 bytes
>>          bInterval 0
>>      Interface Descriptor:
>>        bLength 9
>>        bDescriptorType 4
>>        bInterfaceNumber 1
>>        bAlternateSetting 0
>>        bNumEndpoints 2
>>        bInterfaceClass 255 Vendor Specific Class
>>        bInterfaceSubClass 0
>>        bInterfaceProtocol 0
>>        iInterface 0
>>        Endpoint Descriptor:
>>          bLength 7
>>          bDescriptorType 5
>>          bEndpointAddress 0x83 EP 3 IN
>>          bmAttributes 2
>>            Transfer Type Bulk
>>            Synch Type None
>>            Usage Type Data
>>          wMaxPacketSize 0x0040 1x 64 bytes
>>          bInterval 0
>>        Endpoint Descriptor:
>>          bLength 7
>>          bDescriptorType 5
>>          bEndpointAddress 0x04 EP 4 OUT
>>          bmAttributes 2
>>            Transfer Type Bulk
>>            Synch Type None
>>            Usage Type Data
>>          wMaxPacketSize 0x0040 1x 64 bytes
>>          bInterval 0
>
> Thanks for the details. This isn't a CDC device, so this probably needs
> to be handled by a USB serial driver. What kind of device is it? Does it
> have more than one port?
>
> Judging from the above you should get two ttyUSBx devices if you do:
>
>         # modprobe usbserial
>         # echo 1782 3d00 > /sys/bus/usb-serial/drivers/generic/new_id
>
> as root.
>
> Are those two ports usable?
>
> Thanks,
> Johan



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

  Powered by Linux