Lines Matching refs:SCSI

17 The tmscsim driver supports PCI SCSI Host Adapters based on the AM53C974
18 chip. AM53C974 based SCSI adapters include:
27 scsi = SCSI driver, m = AMD (?) as opposed to w for the DC390W/U/F
57 driver. Of course you have to choose to compile SCSI support and DC390(T)
89 Upgrading a SCSI driver is always a delicate thing to do. The 2.0 driver has
96 * have copies of your SCSI disk's partition tables on some safe location:
101 if your SCSI disk gets corrupted. You can use
113 - SCSI
130 C = Controller, B = Bus, T = Target SCSI ID, U = Unit SCSI LUN.)
139 The "?" should be replaced by the SCSI host number. (The shell might do this
146 Tekram DC390/AM53C974 PCI SCSI Host Adapter, Driver Version 2.0e7 2000-11-28
147 SCSI Host Nr 1, AM53C974 Adapter Nr 0
163 is somehow inconvenient, but the way the mid-level SCSI code expects it to be.
167 adapter and the connected SCSI devices respectively.
170 LUN are the SCSI ID and LUN, Prty means Parity checking, Sync synchronous
178 (The driver allows slightly higher speeds if the devices (Ultra SCSI) accept
217 The first three numbers, "0 0 0" (Device index 0, SCSI ID 0, SCSI LUN 0),
219 would be sufficient to use the index or both SCSI ID and LUN, but I chose
229 (3) Special commands: You can force a SCSI bus reset, an INQUIRY command, the
230 removal or the addition of a device's DCB and a SCSI register dump.
234 (Idx). ADD takes the SCSI ID and LUN.
244 after unmounting its partitions, telling the SCSI mid-level code to
285 * AdaptID: The SCSI ID of the host adapter. Must be in the range 0..7
311 *2 0x04 4 Reset SCSI Bus on startup.
312 *3 0x08 8 Active Negation: Improves SCSI Bus noise immunity.
339 can use tmscsim=7,0,31,63,4,0 for maximum performance, if your SCSI chain
368 recover from a SCSI reset in time. Use a higher delay or don't issue
369 a SCSI bus reset on driver initialization. See problems page.
375 replaced by the dev index of your scanner). You may try to reset your SCSI
387 bad interaction between the Mid-Layer of Linux' SCSI code and the driver.
403 are caused by the SCSI mid-level code.
408 Beware: If your syslog gets written to a SCSI disk connected to your
423 Thanks to Doug Ledford, Gérard Roudier for support with SCSI coding.