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/t128.c | |
parent | 997acab7d593913eaa0606ff257079efcfcb146d (diff) | |
download | linux-stable-3f9e986e2f1df8fa69ffe213098c1ee98f1c9584.tar.gz linux-stable-3f9e986e2f1df8fa69ffe213098c1ee98f1c9584.tar.bz2 linux-stable-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/t128.c')
-rw-r--r-- | drivers/scsi/t128.c | 23 |
1 files changed, 0 insertions, 23 deletions
diff --git a/drivers/scsi/t128.c b/drivers/scsi/t128.c index 4253fe97c210..6220dee8b697 100644 --- a/drivers/scsi/t128.c +++ b/drivers/scsi/t128.c @@ -23,32 +23,9 @@ * 5415 Randall Place * Fremont, CA 94538 * 1+ (415) 770-1400, FAX 1+ (415) 770-9910 - * - * 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 : - * 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. You - * only really want to use this if you're having a problem with - * dropped characters during high speed communications, and even - * then, you're going to be better off twiddling with transfersize. - * * The card is detected and initialized in one of several ways : * 1. Autoprobe (default) - since the board is memory mapped, * a BIOS signature is scanned for to locate the registers. |