Lines Matching refs:SCSI
11 2. Supported chips and SCSI features
13 3.1 Optimized SCSI SCRIPTS
14 3.2 New features of the SYM53C896 (64 bit PCI dual LVD SCSI controller)
38 10.2.5 Ultra SCSI support
52 10.2.19 Check SCSI BUS
54 10.2.21 Suggest a default SCSI id for hosts
59 10.6 SCSI BUS checking boot option
67 14.3 Using only 8 bit devices with a WIDE SCSI controller.
70 15. SCSI problem troubleshooting
74 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers
75 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers
99 the ealiest 810 rev. 1, the latest 896 (2 channel LVD SCSI controller) and
100 the new 895A (1 channel LVD SCSI controller).
107 PCI-HOWTO written by Michael Will and in the SCSI-HOWTO written by
114 SCSI standard documentations are available at SYMBIOS ftp server:
118 Usefull SCSI tools written by Eric Youngdale are available at tsx-11:
128 the proc SCSI file system read / write operations.
142 2. Supported chips and SCSI features
149 SCSI parity checking
158 Chip SDMS BIOS Wide SCSI std. Max. sync driver driver
183 Profiling information: read operations from the proc SCSI file system
184 Control commands: write operations to the proc SCSI file system
194 3.1 Optimized SCSI SCRIPTS.
196 The 810A, 825A, 875, 895, 896 and 895A support new SCSI SCRIPTS instructions
201 modes. The SCSI SCRIPTS had been entirely rewritten using LOAD/STORE instead
204 3.2 New features of the SYM53C896 (64 bit PCI dual LVD SCSI controller)
207 SCRIPTS (avoids the phase mismatch interrupt that stops the SCSI processor
243 Some kown SCSI devices do not properly support tagged command queuing.
260 is currently set to 8 by default. This value is suitable for most SCSI
261 disks. With large SCSI disks (>= 2GB, cache >= 512KB, average seek time
285 In some special conditions, some SCSI disk firmwares may return a
286 QUEUE FULL status for a SCSI command. This behaviour is managed by the
292 - Every 1000 successfully completed SCSI commands, if allowed by the
309 The driver supports SCSI parity checking and PCI bus master parity
312 problems with parity. You can disable either PCI parity or SCSI parity
318 Profiling information is available through the proc SCSI file system.
359 revision ID identify the SCSI chip as follows:
372 The profiling information is updated upon completion of SCSI commands.
392 Number of SCSI disconnections
393 Example above: 25763 SCSI disconnections
408 Elapsed time for SCSI commands setups
416 Elapsed time for SCSI disconnections
421 (time from SCSI status get to command completion call)
435 the proc SCSI file system. The generic command syntax is the
442 apply to all targets of the SCSI chain (except the controller).
500 nego: print information about SCSI negotiations
529 will allow disconnection for all devices on the SCSI bus.
561 if only one has a flaw for some SCSI feature, you can disable the
591 Force synchronous negotiation for all SCSI-2 devices.
592 Some SCSI-2 devices do not report this feature in byte 7 of inquiry
597 you can answer "y". Then, all SCSI devices will never disconnect the bus
598 even while performing long SCSI operations.
694 10.2.5 Ultra SCSI support
719 #factor = 10 Ultra-2 SCSI 40 Mega-transfers / second
720 #factor = 11 Ultra-2 SCSI 33 Mega-transfers / second
721 #factor < 25 Ultra SCSI 20 Mega-transfers / second
722 #factor < 50 Fast SCSI-2
825 10.2.19 Check SCSI BUS
832 0x4: Disable SCSI bus integrity checking.
841 10.2.21 Suggest a default SCSI id for hosts
843 hostid:#x (0 < x < 7) x suggested for hosts SCSI id.
845 If a host SCSI id is available from the NVRAM, the driver will ignore
857 when it arbitrated for the SCSI BUS.
883 SCSI BUS check donnot attach on error buschk:1
961 Host SCSI ID Y Y
962 SCSI parity checking Y Y
964 SCSI devices parameters
999 10.6 SCSI BUS checking boot option.
1001 When this option is set to a non-zero value, the driver checks SCSI lines
1002 logic state, 100 micro-seconds after having asserted the SCSI RESET line.
1003 The driver just reads SCSI lines and checks all lines read FALSE except RESET.
1004 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
1005 RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
1006 Unfortunately, the following common SCSI BUS problems are not detected:
1011 devices, ... may cause a SCSI signal to be wrong when te driver reads it.
1017 SYMBIOS 53C8XX chips are able to arbitrate for the SCSI BUS as soon as they
1020 connected to the SCSI BUS.
1024 competing for the SCSI BUS. By the way, when the chip is using SCSI id 7,
1025 then it will for sure win the next SCSI BUS arbitration.
1041 SCSI BUS bandwidth if the SCRIPTS execution lasts more than 4 micro-seconds.
1046 to stress SCSI devices or for some applications that can gain advantage of
1097 If defined, synchronous negotiation is tried for all SCSI-2 devices.
1104 If defined, SCSI parity checking is enabled.
1172 conforms to 6.8.2 of SCSI-2 specifications. The current behaviour of
1196 14.3 Using only 8 bit devices with a WIDE SCSI controller.
1198 When only 8 bit NARROW devices are connected to a 16 bit WIDE SCSI controller,
1199 you must ensure that lines of the wide part of the SCSI BUS are pulled-up.
1200 This can be achieved by ENABLING the WIDE TERMINATOR portion of the SCSI
1224 from being triggered for the first SCSI MOVE of the phase. This work-around
1229 the context of the SCSI transfer. This data structure is aligned on 8 DWORDS
1232 But the conditions of this bug can be met when a SCSI read command is
1237 when the SCSI DATA IN phase is reentered after a phase mismatch.
1263 15. SCSI problem troubleshooting
1267 Most SCSI problems are due to a non conformant SCSI bus or to buggy
1268 devices. If infortunately you have SCSI problems, you can check the
1271 - SCSI bus cables
1272 - terminations at both end of the SCSI chain
1282 Now, if your SCSI bus is ok, your system have every chance to work
1293 your SCSI bus but often causes problems with buggy devices.
1295 hard disks. Good SCSI hard disks with a large cache gain advantage of
1305 the SCSI Bus.
1329 SCSI ID of the device the controller was talking with at the moment the
1345 Field C : SIST io register (SCSI Interrupt Status)
1346 Bit 0x08 : SGE SCSI GROSS ERROR
1348 on the SCSI BUS that prevents the SCSI protocol from functionning
1351 Indicates that the device released the SCSI BUS when the chip
1353 …indicate the SCSI initiator that an error condition not reportable using the SCSI pro…
1354 Bit 0x02 : RST SCSI BUS Reset
1355 Generally SCSI targets donnot reset the SCSI BUS, although any
1358 SCSI parity error detected.
1359 On a faulty SCSI BUS, any error condition among SGE (0x08), UDC (0x04) and
1360 PAR (0x01) may be detected by the chip. If your SCSI system sometimes
1361 encounters such error conditions, especially SCSI GROSS ERROR, then a SCSI
1367 This register reflects the state of the SCSI control lines the
1370 Actual value of control lines on the SCSI BUS.
1372 Actual value of data lines on the SCSI BUS.
1373 Field G : SXFER SCSI Transfer
1381 SCSI standards, chip cores functionnals and internal driver data structures.
1393 SCSI-2 mode.
1396 1 Mega-transfers/second means 1 MB/s with 8 bits SCSI and 2 MB/s with
1397 Wide16 SCSI.
1399 16.1 Synchronous timings for 53C895, 53C875 and 53C860 SCSI controllers
1447 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers