dtc3x80.txt 1.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243
  1. README file for the Linux DTC3180/3280 scsi driver.
  2. by Ray Van Tassle (rayvt@comm.mot.com) March 1996
  3. Based on the generic & core NCR5380 code by Drew Eckhard
  4. SCSI device driver for the DTC 3180/3280.
  5. Data Technology Corp---a division of Qume.
  6. The 3280 has a standard floppy interface.
  7. The 3180 does not. Otherwise, they are identical.
  8. The DTC3x80 does not support DMA but it does have Pseudo-DMA which is
  9. supported by the driver.
  10. It's DTC406 scsi chip is supposedly compatible with the NCR 53C400.
  11. It is memory mapped, uses an IRQ, but no dma or io-port. There is
  12. internal DMA, between SCSI bus and an on-chip 128-byte buffer. Double
  13. buffering is done automagically by the chip. Data is transferred
  14. between the on-chip buffer and CPU/RAM via memory moves.
  15. The driver detects the possible memory addresses (jumper selectable):
  16. CC00, DC00, C800, and D800
  17. The possible IRQ's (jumper selectable) are:
  18. IRQ 10, 11, 12, 15
  19. Parity is supported by the chip, but not by this driver.
  20. Information can be obtained from /proc/scsi/dtc3c80/N.
  21. Note on interrupts:
  22. The documentation says that it can be set to interrupt whenever the
  23. on-chip buffer needs CPU attention. I couldn't get this to work. So
  24. the driver polls for data-ready in the pseudo-DMA transfer routine.
  25. The interrupt support routines in the NCR3280.c core modules handle
  26. scsi disconnect/reconnect, and this (mostly) works. However..... I
  27. have tested it with 4 totally different hard drives (both SCSI-1 and
  28. SCSI-2), and one CDROM drive. Interrupts works great for all but one
  29. specific hard drive. For this one, the driver will eventually hang in
  30. the transfer state. I have tested with: "dd bs=4k count=2k
  31. of=/dev/null if=/dev/sdb". It reads ok for a while, then hangs.
  32. After beating my head against this for a couple of weeks, getting
  33. nowhere, I give up. So.....This driver does NOT use interrupts, even
  34. if you have the card jumpered to an IRQ. Probably nobody will ever
  35. care.