Greg KH schrieb:
On Tue, Oct 06, 2009 at 05:21:01PM -0700, Matthew Dharm wrote:
On Tue, Oct 06, 2009 at 03:40:35PM -0700, Greg KH wrote:
On Tue, Oct 06, 2009 at 02:24:03PM -0700, Matthew Dharm wrote:
On Tue, Oct 06, 2009 at 11:16:07PM +0200, Peter Magdina wrote:
Imagine you already have some USB serial device plugged and running
and you decide to plug this one. I am not sure, because I don't
have much experiences, but I guess you will have to unload usbserial
module and load it once again with vendor/product params, don't you?
And what will happen with already using other USB device ?
That's a fair criticism. But I think the right thing to do here is to make
usb-serial accept new VID/PIDs without needing to be unloaded/reloaded,
then do everything in userspace.
That works today for all usb devices with the sysfs new_id file. So
nothing needs to be done :)
In that case, we should reject this patch and push all of this into
userspace.
Ok, if it works there, fine :)
It does. As I said the script of usb_modeswitch will add the ID to
"option" after switching via "new_id" (if it's not bound to "cdc_acm").
And in the case of the Toshiba device "eject" should work for
switching as well.
Josua
--
Man is the only creature on earth enabled to take a
warm meal while flying! Loriot
--
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
