Subject: Re: esiop driver
To: Matt Thomas <email@example.com>
From: Manuel Bouyer <firstname.lastname@example.org>
Date: 05/15/2002 10:46:37
On Wed, May 15, 2002 at 01:30:05AM -0700, Matt Thomas wrote:
> At 09:52 AM 5/14/2002, Manuel Bouyer wrote:
> >Interesting. I have a SCSI2 and a SCSI3 device connected to a 1010 (bus in
> >SE mode, though) and some SCSI3 connected to a 895 and I don't have this
> >Maybe your drive has a bug, and claim to only support DT clocking when
> >it's not true ? The attached patch should confirm this.
> That "fixed" the problem but looking throught the scsipi code, I don't
> think DT is handled properly. DT implys WIDE16/SYNC which the code clears.
Yes, and it's because DT implys WIDE16/SYNC that WIDE16/SYNC is used for ST
only. We need a way to tell a drive supports DT clocking but not ST, as
it's allowed by the specs.
> That seems wrong. Also the periph_cap code doesn't about DT and so doesn't
> print correct drive information.
We could use DT as WIDE16+SYNC here. It's easy to add.
> Also, I don't any negotiation is done for
> DT and that's wrong as well.
Because your SCSI adapter doesn't support DT clocking.
Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr