Date: Wed, 07 May 2008 21:17:33 +0200 From: Fredrik Lindberg <fli@shapeshifter.se> To: Steve Clark <sclark@netwolves.com> Cc: Marcin Cieslak <saper@system.pl>, freebsd-usb@freebsd.org Subject: Re: sierra wireless compass 597 aircard (Was: Documentation) Message-ID: <4822004D.4050502@shapeshifter.se> In-Reply-To: <4821F73B.5010501@netwolves.com> References: <481B094F.1090408@netwolves.com> <200805021534.13848.hselasky@c2i.net> <481B5095.8080400@netwolves.com> <fvgbrb$k3u$1@ger.gmane.org> <481C623D.7040902@shapeshifter.se> <4821F73B.5010501@netwolves.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Clark wrote: > Fredrik Lindberg wrote: >> Marcin Cieslak wrote: >> >>> It maybe a good idea to add 0xFFF to the usbdevs. >>> Does the "umass" driver attach to the 0xFFF device? I would >>> recommend adding this as a quirk to umass.c then. >>> >>> There are patches attached (ubsa.c_patch, umass_c.patch, >>> usbdevs.patch) I am using to kill the "zeroconf" CD on the UMTS. They >>> do not always work - i.e. umass_attach does not wait until the device >>> is really detached. But setting USB_DEBUG helps :-) >>> >> >> >> Since your patches deals with Option cards I'll just let you know that >> all(?) Option based devices can be switched perfectly safe from >> user land, without patching ubsa, using camcontrol. >> The command to switch Option devices is a SCSI REZERO command. >> >> This should be enough to switch the device, given that pass0 >> is the modem (use camcontrol devlist) >> >> camcontrol cmd pass0 -c “01 00 00 00 00 00″ -i 1 i1 >> >> camcontrol might give you an error but the device will be switched. >> Note that this is ONLY for Option based devices, I don't know about >> the Sierra ones but the linux usb_modeswitch tool might be a good start. >> >> Fredrik >> >> > Hi Fredrik, > > This does not seem to work for me with the sierra usb device. No, as I said it's for devices from Option (www.option.com). My comment was actually more directed to Marcin since his patches dealt with Option devices. Sorry for the semi thread hijacking. I personally think it's a bad idea to put the code for "switching" these kind of devices inside the kernel. Drivers will become cluttered with switching code for different kinds of devices and it will prevent anybody from actually reading was on the "Zero-CD" device. Besides, I'm quite sure all devices can be switched from user land, one way or another. In my opinion, what's really needed is some sort of generic dynamic black listing which can prevent drivers from attaching to devices. For usb devices one can then simply send the magic switch sequences through a ugen device. The usb_modeswitch tool does exactly that. Fredrik
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4822004D.4050502>