Alan Stern wrote:
The current strategy is to avoid vendor-specific interface classes and
Microsoft RNDIS, and to use the first otherwise available configuration.
(The numbering is ignored totally.) That's why you end up with the
high-power config.
This is completely devastating.
There *must* be a match of the power requirements of the configuration
and the port. Currently the device gets configured with a high power
configuration on a low power port.
This can trigger the overcurrent protection of a bus powered hub which
usually then switches off completely dragging down three other innocent
devices.
Please tell me that Linux kernel programmers are not that idiotic.
(for the record: i posted before i confirmed my subscription)
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
