On Wed, Nov 16, 2016 at 10:03:52PM +0100, Giuseppe Lippolis wrote: > Dear All, > thanks for the very interesting discussion. > > > > This will make option grab all the ports, as shown by your dmesg > > > output. But USB interfaces 0 and 1 are actually cdc-ether and should > > > *not* be grabbed by option. > > > > > > You want to limit option to grabbing bInterfaceClass=255 to make sure > > > it only gets the serial ports. > > > > Actually the device have 2 cdc_ether interface and the others are serial comm. > This is the bootlog of the original oem firmware: > > hub 2-0:1.0: USB hub found > hub 2-0:1.0: 1 port detected > usb 2-1: new high speed USB device using rt3xxx-ehci and address 2 > usb 2-1: configuration #1 chosen from 1 choice > usbcore: registered new interface driver cdc_ether > usbcore: registered new interface driver usbserial > drivers/usb/serial/usb-serial.c: USB Serial support registered for generic > usbserial_generic 2-1:1.2: generic converter detected > usb 2-1: generic converter now attached to ttyUSB0 > usbserial_generic 2-1:1.3: generic converter detected > usb 2-1: generic converter now attached to ttyUSB1 > usbserial_generic 2-1:1.4: generic converter detected > usb 2-1: generic converter now attached to ttyUSB2 > usbserial_generic 2-1:1.5: generic converter detected > usb 2-1: generic converter now attached to ttyUSB3 > usbserial_generic 2-1:1.6: generic converter detected > usb 2-1: generic converter now attached to ttyUSB4 > usbcore: registered new interface driver usbserial_generic > drivers/usb/serial/usb-serial.c: USB Serial Driver core > > and at the end of the modem configuration: > usbnet0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx > inet addr:77.25.169.193 Bcast:77.25.169.195 Mask:255.255.255.252 > inet6 addr: fe80::ffff:feaa:aaaa/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:6 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:272 (272.0 B) TX bytes:600 (600.0 B) > > Therefore I also consider convenient preserve the first two interface > for the cdc_ether. > Can you please clarify me the differences between black and white list > and how to configure it? If possible you want to tell the option driver which interfaces to bind to (white-listing) rather than specifying which not to bind to (black-listing). The latter typically means probing all interfaces, checking the black list, and then bailing out for unsupported interfaces. By matching on the interface class it is sometimes possible to rely solely on white-listing, for example: USB_DEVICE_INTERFACE_CLASS(VID, PID, 0xff) would (only) bind to all interface with Vendor Specific Class. 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
