Re: [PATCH] ar9170usb: add mode-switching for AVM Fritz!WLAN USB N devices in cdrom mode

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

 



On Tue, 2009-11-03 at 08:48 +0100, Josua Dietze wrote:
> Dan Williams schrieb:
> 
>  
> > Devices with fake driver CDs and how they are handled currently:
> > 
> > Zydas WLAN   - kernel
> > Huawei 3G    - kernel  (unusual_devs entry)
> > Sierra 3G    - kernel  (drivers/usb/serial/sierra.c)
> > Option 3G    - udev rules, 'rezero', or usb_modeswitch
> > ZTE 3G       - udev rules, simple 'eject'
> 
> Some corrections:
> 
> * Huawei 3G: all devices that are handled in the kernel can be 
> switched outside too (usb_modeswitch). Newer Huawei devices have a 
> different mechanism which is so far only handled by usb_modeswitch.
> 
> * Sierra 3G: can be switched by usb_modeswitch as well.
> 
> * Option 3G: can be switched by usb_modeswitch (has been there for 
> quite a while before the kernel patch came in). One device family 
> needed a patch in the patch because the kernel switch affected the 
> wrong devices (ambiguous ID). These ambiguities can be handled by 
> usb_modeswitch by easily adding ID checks for SCSI_INQUIRY strings 
> and USB device data like "manufacturer", "vendor", "model" etc.
> 
> * ZTE 3G: some ZTE devices are using a different command than 
> "eject". Handled by usb_modeswitch.
> 
> The bottom line is that the imagination of the device developer has 
> no limit, so in my view - duct tape and libusb junk included - the 
> userspace is just able to react *a lot quicker* than the kernel space.

This is true, but for usb_modeswitch to become really useful to
distributors, it needs to Just Work without end-user configuration.
That means uncommenting all the devices in the config file, and when
usb_modeswitch is run, it needs to scan the bus for any modem that it's
configuration knows about, and eject it.

The problem with usb_modeswitch now is that even after installing it and
its udev rules, the user has to manually uncomment the item in the
config file for their specific modem, which will never just work out of
the box.

Or am I somewhat out-of-date?  That was the status as of earlier this
summer (July) when I looked into it.

My idea situation is probably just to use usb_modeswitch, but as a
distribution packager (for Fedora) I need the tool to work automatically
whenever anyone plugs in a modem that usb_modeswitch knows about,
instead of requiring that user to modify a config file.

Cheers,
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

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

  Powered by Linux