diff options
Diffstat (limited to 'Documentation/scsi/tmscsim.txt')
| -rw-r--r-- | Documentation/scsi/tmscsim.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/scsi/tmscsim.txt b/Documentation/scsi/tmscsim.txt index df7a02bfb5bf..8b2168aa4fc7 100644 --- a/Documentation/scsi/tmscsim.txt +++ b/Documentation/scsi/tmscsim.txt | |||
| @@ -27,7 +27,7 @@ Tekram DC390(T) adapter. This is where the name comes from: tm = Tekram | |||
| 27 | scsi = SCSI driver, m = AMD (?) as opposed to w for the DC390W/U/F | 27 | scsi = SCSI driver, m = AMD (?) as opposed to w for the DC390W/U/F |
| 28 | (NCR53c8X5, X=2/7) driver. Yes, there was also a driver for the latter, | 28 | (NCR53c8X5, X=2/7) driver. Yes, there was also a driver for the latter, |
| 29 | tmscsiw, which supported DC390W/U/F adapters. It's not maintained any more, | 29 | tmscsiw, which supported DC390W/U/F adapters. It's not maintained any more, |
| 30 | as the ncr53c8xx is perfectly supporting these adpaters since some time. | 30 | as the ncr53c8xx is perfectly supporting these adapters since some time. |
| 31 | 31 | ||
| 32 | The driver first appeared in April 1996, exclusively supported the DC390 | 32 | The driver first appeared in April 1996, exclusively supported the DC390 |
| 33 | and has been enhanced since then in various steps. In May 1998 support for | 33 | and has been enhanced since then in various steps. In May 1998 support for |
| @@ -381,7 +381,7 @@ Please see http://www.garloff.de/kurt/linux/dc390/problems.html | |||
| 381 | replaced by the dev index of your scanner). You may try to reset your SCSI | 381 | replaced by the dev index of your scanner). You may try to reset your SCSI |
| 382 | bus afterwards (echo "RESET" >/proc/scsi/tmscsim/?). | 382 | bus afterwards (echo "RESET" >/proc/scsi/tmscsim/?). |
| 383 | The problem seems to be solved as of 2.0d18, thanks to Andreas Rick. | 383 | The problem seems to be solved as of 2.0d18, thanks to Andreas Rick. |
| 384 | * If there is a valid partition table, the driver will use it for determing | 384 | * If there is a valid partition table, the driver will use it for determining |
| 385 | the mapping. If there's none, a reasonable mapping (Symbios-like) will be | 385 | the mapping. If there's none, a reasonable mapping (Symbios-like) will be |
| 386 | assumed. Other operating systems may not like this mapping, though | 386 | assumed. Other operating systems may not like this mapping, though |
| 387 | it's consistent with the BIOS' behaviour. Old DC390 drivers ignored the | 387 | it's consistent with the BIOS' behaviour. Old DC390 drivers ignored the |