On Tue, 7 Oct 2014, Emiliano Vazquez wrote:

El 06/10/14 a las 12:42, David Lang escibió:
what does 'lsusb -v -s 3:3' and -s 3:4 show on Ubuntu?


First you need to know this:
I have severals usb to serial adapters. All of those have the same HL-340 chipset. when i plug two of this serials i get only information in Bus 003 Device 002 and Device 003. This give me a possibility to do lsub -v -s 3:2 and lsusb -v 3:3 Then i take out one device and put another and get Bus 003 Device 003 and Device 004 If i take out both and replug then i will need lsusb -v -s 3:5 and lsusb -v -s 3:6
It's like an incremental device ? I don't know.

Yep, each time you connect it, it shows as a new device, and if the system hasn't completely timed out and disconnected the old device, it gets assigned a new id (and since there is no message to the system when a device is disconnected, this can be a very long timeout)

David, this is the output on Ubuntu

yep, nothing unique, so there is no reliable way to tell them apart.

If there is some way to alter the firmware on these devices to set a serial number you could do it (see the current handwringing over "Bad USB" as an example), but other than that you are going to have problems. I would suggest looking for another brand of cheap adapter so that you can use one of each brand so that you can tell them apart.

David Lang


lsusb -v -s 3:3

Bus 003 Device 003: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Couldn't open device, some information will be missing
Device Descriptor:
 bLength                18
 bDescriptorType         1
 bcdUSB               1.10
 bDeviceClass          255 Vendor Specific Class
 bDeviceSubClass         0
 bDeviceProtocol         0
 bMaxPacketSize0         8
 idVendor           0x1a86 QinHeng Electronics
 idProduct          0x7523 HL-340 USB-Serial adapter
 bcdDevice            2.54
 iManufacturer           0
 iProduct                2
 iSerial                 0
 bNumConfigurations      1
 Configuration Descriptor:
   bLength                 9
   bDescriptorType         2
   wTotalLength           39
   bNumInterfaces          1
   bConfigurationValue     1
   iConfiguration          0
   bmAttributes         0x80
     (Bus Powered)
   MaxPower               96mA
   Interface Descriptor:
     bLength                 9
     bDescriptorType         4
     bInterfaceNumber        0
     bAlternateSetting       0
     bNumEndpoints           3
     bInterfaceClass       255 Vendor Specific Class
     bInterfaceSubClass      1
     bInterfaceProtocol      2
     iInterface              0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x82  EP 2 IN
       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     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            3
         Transfer Type            Interrupt
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0008  1x 8 bytes
       bInterval               1

lsusb -v -s 3:2

Bus 003 Device 002: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Couldn't open device, some information will be missing
Device Descriptor:
 bLength                18
 bDescriptorType         1
 bcdUSB               1.10
 bDeviceClass          255 Vendor Specific Class
 bDeviceSubClass         0
 bDeviceProtocol         0
 bMaxPacketSize0         8
 idVendor           0x1a86 QinHeng Electronics
 idProduct          0x7523 HL-340 USB-Serial adapter
 bcdDevice            2.54
 iManufacturer           0
 iProduct                2
 iSerial                 0
 bNumConfigurations      1
 Configuration Descriptor:
   bLength                 9
   bDescriptorType         2
   wTotalLength           39
   bNumInterfaces          1
   bConfigurationValue     1
   iConfiguration          0
   bmAttributes         0x80
     (Bus Powered)
   MaxPower               96mA
   Interface Descriptor:
     bLength                 9
     bDescriptorType         4
     bInterfaceNumber        0
     bAlternateSetting       0
     bNumEndpoints           3
     bInterfaceClass       255 Vendor Specific Class
     bInterfaceSubClass      1
     bInterfaceProtocol      2
     iInterface              0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x82  EP 2 IN
       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     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            3
         Transfer Type            Interrupt
         Synch Type               None
         Usage Type               Data
       wMaxPacketSize     0x0008  1x 8 bytes
       bInterval               1

this is only one difference: the line who talks about the Bus!

I would say that the openwrt serial shown by udevadm info is faulty, but I suspect that the Ubuntu one is faulty as well, just in a different way.
It's true.

Best regards.



_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users

Reply via email to