In my experience, resetting is rare. If you do need it, it's probably because the device isn't compliant and wasn't going to work anyway.
So, why don't we just move the reset into the core, and then every driver
(including usb-storage) can get reset all at once? That sidesteps the
issue, I think.
Matt
On Thu, Mar 20, 2003 at 09:01:49PM +0100, Oliver Neukum wrote:
>
> > I've actually been thinking along those lines, too... but, given the new
> > design where devices aren't 'remembered', doing the above would disconnect
> > a device and create a new one (as seen by the user). It kinda defeats the
> > entire purpose of the reset (which is to try to get back to a good state).
> >
> > My guess is that we just have to make a decision on reset-recovery: Is it
> > worth it? If not, let's just implement Alan's suggestion and be done with
> > it.
>
> Well, you have a lot of storage devices. Do you need resetting for a working
> error recovery? If so we probably need it. A robust system needs some form
> of error recovery.
>
> As a practical matter we could limit resetting to devices with only one
> interface, which is the vast majority (strictly speaking this needs to be
> locked against configuration changes). In this case the disconnect/probe
> cycle can be dropped.
>
> Regards
> Oliver
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
E: You run this ship with Windows?! YOU IDIOT!
L: Give me a break, it came bundled with the computer!
-- ESR and Lan Solaris
User Friendly, 12/8/1998
pgp00000.pgp
Description: PGP signature
