On Tue, May 27, 2003, David Brownell [EMAIL PROTECTED] wrote:
Johannes Erdfelt wrote:
I think it should change for 2.5 and 2.4.
I agree that a kernel patch is the right thing here,
maybe even for 2.2 ... but specifically what patch?
I think changing usbfs to swap those u16 values in
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
Johannes Erdfelt wrote:
Perhaps for 2.5 we should avoid the swap in the core and fix the
drivers.
That's the question ... although it may also be OK to
just live with that one API wart, since I think only
the device descriptor has that (documented?) issue.
We'd need a good tester with a big-endian
Until my ambitious project gets going, this patch at least fixes the
problem of assigning a device's new address following a device reset.
The only change needed to David's original suggestion was to handle the
pathway involved in registering root hubs.
Alan Stern
= drivers/usb/core/hcd.c
On Tue, 27 May 2003, Jochen Friedrich wrote:
Even worse, the patch caused an instant reboot of the PC when trying to
mount the card, so no logs are available :-(.
Oh well... it was worth a try. I am kind of surprised the reaction was so
violent. Is there any possibility of setting up a
Hi Alan,
I think ultimately the fix will be Andries' project to change the SCSI
drivers to use MODE-SENSE(10) instead of MODE-SENSE(6) whenever possible.
Although even that might not help with your device.
I commented the whole cache probe in sd.c (using the default value of
write-through)
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
