My take on things is that adding things to the quirk table is a bit of a
tail chasing exercise. You should do it if you expect the disks to show
up on all platforms. But this case is much more one of "these disks were
shipped with SS1, SS2 and SS10 and nobody will see them much outside of
sun pizza box".

-matt


On Fri, 6 Sep 2002, Izumi Tsutsui wrote:

> In article <20020906013225.60CFCAC@proven.weird.com>
> woods@weird.com wrote:
> 
> > Please do not do that unless it's done across the board for all host
> > adapters on all platforms where drives of a similar vintage might be
> > used.  This is most definitely _NOT_ a sparc or esp specific issue.  The
> > scsipi quirk table should be able to handle this issue for every port
> > and every scsipi-enabled driver uniformly and thus no scsipi-enabled
> > driver need have tagged queuing disabled by default.
> 
> If the drive which doesn't work on ESP200 also has the same problem
> on other adapters it should be listed on the quirk table,
> but otherwise it shouldn't.
> It is not clear which of drives or esp driver have the problem.
> 
> BTW, it seems ESP200 has 40MHz clock but both esp_sbus.c and
> esp_obio.c do not handle FASTSCSI stuff. (see dev/tc/asc_tcds.c)
> If ESP200 on sparc has the same spec with NCR53CF9x, it might
> cause problem on sync transfers and it is MD driver's problem.
> (not tagged queuing related, though.)
> ---
> Izumi Tsutsui
> tsutsui@ceres.dti.ne.jp
>