diff options
| author | Finn Thain <fthain@telegraphics.com.au> | 2014-11-12 16:11:55 +1100 |
|---|---|---|
| committer | Christoph Hellwig <hch@lst.de> | 2014-11-20 09:11:06 +0100 |
| commit | 3f9e986e2f1df8fa69ffe213098c1ee98f1c9584 (patch) | |
| tree | 56371541bd19ebaefaa05426a1d9f0b8a21af197 /drivers/scsi/pas16.c | |
| parent | 997acab7d593913eaa0606ff257079efcfcb146d (diff) | |
| download | talos-obmc-linux-3f9e986e2f1df8fa69ffe213098c1ee98f1c9584.tar.gz talos-obmc-linux-3f9e986e2f1df8fa69ffe213098c1ee98f1c9584.zip | |
ncr5380: Remove duplicate comments
The LIMIT_TRANSFERSIZE, PSEUDO_DMA, PARITY and UNSAFE options are all
documented in the core drivers where they are used. The same goes for the
chip databook reference. Remove the duplicate comments.
Signed-off-by: Finn Thain <fthain@telegraphics.com.au>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'drivers/scsi/pas16.c')
| -rw-r--r-- | drivers/scsi/pas16.c | 31 |
1 files changed, 0 insertions, 31 deletions
diff --git a/drivers/scsi/pas16.c b/drivers/scsi/pas16.c index 7621205e4aa0..3e40479ebb48 100644 --- a/drivers/scsi/pas16.c +++ b/drivers/scsi/pas16.c @@ -22,40 +22,9 @@ * Media Vision * (510) 770-8600 * (800) 348-7116 - * - * and - * - * NCR 5380 Family - * SCSI Protocol Controller - * Databook - * - * NCR Microelectronics - * 1635 Aeroplaza Drive - * Colorado Springs, CO 80916 - * 1+ (719) 578-3400 - * 1+ (800) 334-5454 */ /* - * Options : - * LIMIT_TRANSFERSIZE - if defined, limit the pseudo-dma transfers to 512 - * bytes at a time. Since interrupts are disabled by default during - * these transfers, we might need this to give reasonable interrupt - * service time if the transfer size gets too large. - * - * PSEUDO_DMA - enables PSEUDO-DMA hardware, should give a 3-4X performance - * increase compared to polled I/O. - * - * PARITY - enable parity checking. Not supported. - * - * UNSAFE - leave interrupts enabled during pseudo-DMA transfers. This - * parameter comes from the NCR5380 code. It is NOT unsafe with - * the PAS16 and you should use it. If you don't you will have - * a problem with dropped characters during high speed - * communications during SCSI transfers. If you really don't - * want to use UNSAFE you can try defining LIMIT_TRANSFERSIZE or - * twiddle with the transfer size in the high level code. - * * The card is detected and initialized in one of several ways : * 1. Autoprobe (default) - There are many different models of * the Pro Audio Spectrum/Studio 16, and I only have one of |
