--M/SuVGWktc5uNpra
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 14, 2003 at 12:47:51PM +0000, Sergio Jimenez wrote:
> I'm not sure, I'm not a programmer, and correct me if I'm wrong
> please but...is this file for wdc driver or is it for both wd &
> wdc drivers...

wdc is the driver for the Winchester Device Controller, and wd for
the drives itself.

Any timeouts for probing and recognizing devices would be in wdc,
regardless of whether or not its a drive-specific quirk.

You sure you changed the same timeout?

Not sure I love the idea of making the timeout to probe devices on
wdc several orders of magnitude longer just because one vendor's
device doesn't respond quickly enough (which would be why that patch
never made it into the mainstream). Unfortunately, this can't just
be a regular quirk (since you don't know whether or not you're
dealing with the broken hardware till after you've detected it).

You may want to file a PR referencing the older one.

--=20
gabriel rosenkoetter
gr@eclipsed.net

--M/SuVGWktc5uNpra
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQE/jAfz9ehacAz5CRoRAsNmAKCoKCX6he2fICubRrFYirGTTFRJogCfS6c5
GzuwEe7FGed5QOzzJF9WO4U=
=II/s
-----END PGP SIGNATURE-----

--M/SuVGWktc5uNpra--