Yes, I did'nt black list any vendor specific interfaces in this case because we know (thanks to LOM) how windows driver defines each device interface, look at the following post: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?p=14733#p14733 MI_00 Network Connect Mobile Broadband Device M...

Pheraps it was a better choice by adding USB_VENDOR_AND_INTERFACE_INFO... because it is based just on the VendorId and class/subcl/prot specs.... And If we plugin an other "2020" vendor device, well it should bind option to the right interface out the box even if it has a different Produc...

Ok, I cutted away entries in define section, just added a comment at the end of USB_DEVICE_INTERFACE_CLASS line. I think could be useful to find what device refers that IDs... 1686 .driver_info = (kernel_ulong_t)&net_intf6_blacklist }, 1687 { USB_DEVICE(OLIVETTI_VENDOR_ID, OLIVETTI_PRODUCT_OLICA...

Ok, I've edited option.c as follows (I've just added 4 new lines: a comment, two define lines for Vid an Pid and a line for binding based on interface class): 393 #define OLIVETTI_PRODUCT_OLICARD500 0xc00b 394 395 /* Olicard300 MT6225 */ 396 #define OLICARD300_VENDOR_ID 0x2020 <------- 397 #define O...

Thank you a lot! :D I can now better understand how it works.... As I already said, I'm not a programmer, but I've found where is defined that function (or whaterver it is...): http://lxr.free-electrons.com/source/include/linux/usb.h#L954 954 #define USB_VENDOR_AND_INTERFACE_INFO(vend, cl, sc, pr) \...

I'm trying to better understand why my linux-friendly Huawei-E353 device is recognized without any particular config needed, this aspect could be useful to better understand the "option" driver behaviour on the Olicard-300. Let's try a very easy test: - Unload option, cdc_mbim, qmi_wwan # ...

I've done... I've modify the option.c module source. Then I've rebuild kernel modules and finally reinstall. Now, when I plug Olicard-300 in, all interfaces are managed by proper driver. Here what usb-devices returns: T: Bus=02 Lev=02 Prnt=04 Port=00 Cnt=01 Dev#= 9 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=e...

This is due to white listing in the option driver, based on usb vendor id and interface attributes. You will only be able to use options white/black listing of interfaces if the device is supported in the option driver, the new_id function with on-the-fly support has no info about which interfaces ...

1- If neither option nor cdc-mbim module are already loaded: [root@darkstar ~]# lsmod |grep "option\|cdc" [root@darkstar ~]# Let's plug the dongle in.... a) /var/log/messages: Apr 20 18:03:52 darkstar kernel: [28162.221000] usb 2-4.1: new high-speed USB device number 32 using ehci-pci Apr ...

I've tried an other solution for testing purposes of all Olicard features, included direct ethernet broadband connection. As I explained above, my actual system is too old and doesn't support thees new features: we need cdc-mbim module to manage the dongle... So I've decided to upgrade my kernel to ...

Just a quick update about a UDEV rule I written: # cat 89-olicard-option-driver.rules SUBSYSTEMS=="usb", ATTRS{idVendor}=="2020", ATTRS{idProduct}=="4000", ATTRS{manufacturer}=="Network Connect", ATTRS{product}=="MT6225 ", RUN+="/bin/sh -c '/sbi...

Yes that is clear! :) I'll do an other test on Jessie as soon as possible and report what exactly happens and how many "ttyUSB*" (and which exactly) are created. Anyway I'm interseted in learning something more by your infos. 1) Can you explain me where did you obtain this report? MI_00 Ne...

Hi! First of all, after re-testing serial device /dev/ttyUSB* with AT commands, I can confirm what you said about the five "interfaces" generated at option module loading. For modem use I can regularly communicate with "ttyUSB2" and use it for PPP dial-up connection. In my first ...

Ok, this is the new config file followed by usb_modeswitch log: # Olicard_300 DefaultVendor = 0x2020 DefaultProduct = 0x0002 TargetVendor = 0x2020 TargetProduct = 0x4000 MessageContent = "555342430820298900000000000003f0010100000000000000000000000000" USB_ModeSwitch log from Tue Apr 14 18:...

Thanks a lot for your quick answer! :) Just a note: now I'm connected to internet using the olicard300 with "usbserial" module and I'm writing from the old slackware system, so I'm not using "option" module, because the key did'nt work with that... as I explained in my post above...