Alan Stern wrote:
On Wed, 28 May 2003, David Brownell wrote:
Right now there's
one great big usb_new_device() routine that mixes up
two very different stages
- set address, fetch device and config descriptors
- set configuration, update sysfs
The update sysfs should be part of
Alan Stern wrote:
(1) We don't want connect processing
(registering interfaces in the driver model and probing device drivers,
maybe other things too) and/or disconnect processing (detaching drivers
and deregistering interfaces, etc.) to occur simultaneously in different
threads.
Why not?
Alan Stern wrote:
I want to propose a reorganization of the way the USB core handles device
resets, configuration changes, connects, and disconnects. The motivation
for this is to fix a number of weaknesses in the way device resets and
configuration changes are currently being handled. A good
Am Dienstag, 27. Mai 2003 22:35 schrieb David Brownell:
Alan Stern wrote:
I want to propose a reorganization of the way the USB core handles device
resets, configuration changes, connects, and disconnects. The motivation
for this is to fix a number of weaknesses in the way device resets
Reset and config changes are inherently ugly because they are a break
in a model of interfaces by being operations on devices. Firmware
downloading belongs into the same category.
Altsetting changes don't break it, but I don't know of any
particular issues there any more either.
Someone should
