Alan Stern schrieb:
On Wed, 4 Nov 2009, Johannes Berg wrote:
I think you forgot to consider the case where both the driver and the
mode switch code need an update to handle a new device. This is relevant
in the case where a new device shows up that needs mode-switching, but
even after switching has an ID that the current driver doesn't know
about.
This could be handled by programs like usb_modeswitch. The USB serial
drivers allow IDs to be added dynamically.
Of course, if something more than that is required then the situation
would be different. However I think this is pretty rare.
So far, mostly cdc_acm and high speed serial devices are known.
There is the special case of the HSO interface for "Option" modems
which resembles a network device IIRC. But switching them is pretty
straightforward and driver support by the manufacturer seems to be OK.
I don't know of any "switching" devices which are completely
unsupported by the recent kernels.
usb_modeswitch now has a wrapper which loads the "option" module by
default if the "new" device will not be claimed by "cdc_acm", "hso"
or "option". Using the "new_id" feature *any* ID can be used with it
right away.
Josua Dietze
--
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-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
