On Mon, 2011-06-13 at 17:01 +0200, Marius Kotsbak wrote: > On 13. juni 2011 16:57, Dan Williams wrote: > > On Sat, 2011-06-11 at 01:34 +0200, Marius B. Kotsbak wrote: > >> Introducing driver for the network port of Samsung Kalmia based USB LTE modems. > >> It has also an ACM interface that previous patches associates with the "option" > >> module. To access those interfaces, the modem must first be switched from modem > >> mode using a tool like usb_modeswitch. > >> > >> As the proprietary protocol has been discovered by watching the MS Windows driver > >> behavior, there might be errors in the protocol handling, but stable and fast > >> connection has been established for hours with Norwegian operator NetCom that > >> distributes this modem with their LTE/4G subscription. > > Why make the driver bind to both the switched and unswitched USB IDs? > > Shouldn't the kernel bind the driver after switch when the device > > reconnects with the new IDs? > > No, I tried and it did not happen, so I assumed that the kernel modules > are only loaded at USB insertion event, not when the interfaces changes. > Does anyone here know if my observation is right? > > Usb_modeswitch autoloads "option" module after switching, but not my > kalmia module. Try killing the modeswitch autoload thing first by moving the udev script out of the way. Then plug your device in, and run "usb-modeswitch -c /path/to/config" so that the usb_modeswitch autoload thing doesn't run. Does that work? I don't want to slander usb_modeswitch but I've seen some odd behavior which I suspect is it's module force-loading feature, though I haven't investigated too much yet. But ruling that out could be helpful. Dan -- 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
