[snip]

   > Here's what dmesg reports:
   > 
   >   siop0 at pci0 dev 11 function 0: Symbios Logic 53c875 (ultra-wide scsi)
   >   siop0: using on-board RAM
   >   siop0: interrupting at irq 10

   Hum, ok so this board is based on a wide chip but only the narrow connector
   is used. Sure, with a wide disk the driver will negotiate wide transfers
   and try to use them; there's no fall-back mechanism (hum depending on how
   things are setup I'm not sure transfers will fail, they may just transfer
   incorrect data with highter bits all 0 or all 1). I'm not sure how to handle
   this; this is a quite unusual setup.

   --
   Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
   --


The Diamond Fireport 20 is the same way.  It is basically a Fireport 40
[Ultra Wide] without the wide connector on it.  With the NCR driver it
probes as follows:

ncr1 at pci0 dev 9 function 0: ncr 53c875j fast20 wide scsi
ncr1: interrupting at irq 10
ncr1: minsync=25, maxsync=254, maxoffs=16, 128 dwords burst, large dma fifo
ncr1: single-ended, open drain IRQ driver, using on-chip SRAM
ncr1: restart (scsi reset).
scsibus1 at ncr1: 16 targets, 8 luns per target


I don't know what would happen if I hooked up a Wide drive to this
controller.  Technically the card isn't really a wide-enabled card.




Brad Spencer - brad@anduin.eldar.org   http://anduin.eldar.org
[finger brad@anduin.eldar.org for PGP public key]