Lines Matching refs:SCSI
18 2. Supported chips and SCSI features
20 3.1 Optimized SCSI SCRIPTS
21 3.2 New features of the SYM53C896 (64 bit PCI dual LVD SCSI controller)
45 10.2.5 Ultra SCSI support
59 10.2.19 Check SCSI BUS
61 10.2.21 Suggest a default SCSI id for hosts
66 10.6 SCSI BUS checking boot option
74 14.3 Using only 8 bit devices with a WIDE SCSI controller.
77 15. SCSI problem troubleshooting
81 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers
82 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers
107 the earliest 810 rev. 1, the latest 896 (2 channel LVD SCSI controller) and
108 the new 895A (1 channel LVD SCSI controller).
115 PCI-HOWTO written by Michael Will and in the SCSI-HOWTO written by
122 SCSI standard documentations are available at SYMBIOS ftp server:
126 Useful SCSI tools written by Eric Youngdale are available at tsx-11:
136 the proc SCSI file system read / write operations.
152 2. Supported chips and SCSI features
160 - SCSI parity checking
170 |Chip |SDMS BIOS |Wide |SCSI std. | Max. sync |driver |driver |
211 :Profiling information: read operations from the proc SCSI file system
212 :Control commands: write operations to the proc SCSI file system
224 3.1 Optimized SCSI SCRIPTS
227 The 810A, 825A, 875, 895, 896 and 895A support new SCSI SCRIPTS instructions
232 modes. The SCSI SCRIPTS had been entirely rewritten using LOAD/STORE instead
235 3.2 New features of the SYM53C896 (64 bit PCI dual LVD SCSI controller)
239 SCRIPTS (avoids the phase mismatch interrupt that stops the SCSI processor
278 Some known SCSI devices do not properly support tagged command queuing.
295 is currently set to 8 by default. This value is suitable for most SCSI
296 disks. With large SCSI disks (>= 2GB, cache >= 512KB, average seek time
320 In some special conditions, some SCSI disk firmwares may return a
321 QUEUE FULL status for a SCSI command. This behaviour is managed by the
327 - Every 1000 successfully completed SCSI commands, if allowed by the
348 The driver supports SCSI parity checking and PCI bus master parity
351 problems with parity. You can disable either PCI parity or SCSI parity
358 Profiling information is available through the proc SCSI file system.
398 revision ID identify the SCSI chip as follows:
413 The profiling information is updated upon completion of SCSI commands.
433 Number of SCSI disconnections
434 Example above: 25763 SCSI disconnections
449 Elapsed time for SCSI commands setups
457 Elapsed time for SCSI disconnections
462 (time from SCSI status get to command completion call)
477 the proc SCSI file system. The generic command syntax is the
484 apply to all targets of the SCSI chain (except the controller).
555 nego print information about SCSI negotiations
589 will allow disconnection for all devices on the SCSI bus.
628 if only one has a flaw for some SCSI feature, you can disable the
654 Force synchronous negotiation for all SCSI-2 devices.
656 Some SCSI-2 devices do not report this feature in byte 7 of inquiry
661 you can answer "y". Then, all SCSI devices will never disconnect the bus
662 even while performing long SCSI operations.
780 10.2.5 Ultra SCSI support
823 #factor = 10 Ultra-2 SCSI 40 Mega-transfers / second
824 #factor = 11 Ultra-2 SCSI 33 Mega-transfers / second
825 #factor < 25 Ultra SCSI 20 Mega-transfers / second
826 #factor < 50 Fast SCSI-2
990 10.2.19 Check SCSI BUS
1001 0x4: Disable SCSI bus integrity checking.
1013 10.2.21 Suggest a default SCSI id for hosts
1018 hostid:#x (0 < x < 7) x suggested for hosts SCSI id.
1021 If a host SCSI id is available from the NVRAM, the driver will ignore
1038 when it arbitrated for the SCSI BUS.
1068 SCSI BUS check do not attach on error buschk:1
1159 | * Host SCSI ID | Y | Y |
1161 | * SCSI parity checking | Y | Y |
1165 |SCSI devices parameters |
1210 10.6 SCSI BUS checking boot option.
1213 When this option is set to a non-zero value, the driver checks SCSI lines
1214 logic state, 100 micro-seconds after having asserted the SCSI RESET line.
1215 The driver just reads SCSI lines and checks all lines read FALSE except RESET.
1216 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
1217 RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
1218 Unfortunately, the following common SCSI BUS problems are not detected:
1225 devices, ... may cause a SCSI signal to be wrong when te driver reads it.
1232 SYMBIOS 53C8XX chips are able to arbitrate for the SCSI BUS as soon as they
1235 connected to the SCSI BUS.
1239 competing for the SCSI BUS. By the way, when the chip is using SCSI id 7,
1240 then it will for sure win the next SCSI BUS arbitration.
1256 SCSI BUS bandwidth if the SCRIPTS execution lasts more than 4 micro-seconds.
1261 to stress SCSI devices or for some applications that can gain advantage of
1319 If defined, synchronous negotiation is tried for all SCSI-2 devices.
1327 If defined, SCSI parity checking is enabled.
1400 conforms to 6.8.2 of SCSI-2 specifications. The current behaviour of
1425 14.3 Using only 8 bit devices with a WIDE SCSI controller
1428 When only 8 bit NARROW devices are connected to a 16 bit WIDE SCSI controller,
1429 you must ensure that lines of the wide part of the SCSI BUS are pulled-up.
1430 This can be achieved by ENABLING the WIDE TERMINATOR portion of the SCSI
1456 from being triggered for the first SCSI MOVE of the phase. This work-around
1461 the context of the SCSI transfer. This data structure is aligned on 8 DWORDS
1465 But the conditions of this bug can be met when a SCSI read command is
1470 when the SCSI DATA IN phase is reentered after a phase mismatch.
1472 15. SCSI problem troubleshooting
1478 Most SCSI problems are due to a non conformant SCSI bus or to buggy
1479 devices. If unfortunately you have SCSI problems, you can check the
1482 - SCSI bus cables
1483 - terminations at both end of the SCSI chain
1493 Now, if your SCSI bus is ok, your system have every chance to work
1504 your SCSI bus but often causes problems with buggy devices.
1506 hard disks. Good SCSI hard disks with a large cache gain advantage of
1522 the SCSI Bus.
1550 SCSI ID of the device the controller was talking with at the moment the
1569 Field C : SIST io register (SCSI Interrupt Status)
1571 Bit 0x08 SGE SCSI GROSS ERROR
1573 on the SCSI BUS that prevents the SCSI protocol from functioning
1576 Indicates that the device released the SCSI BUS when the chip
1578 indicate the SCSI initiator that an error condition not reportable
1579 using the SCSI protocol has occurred.
1580 Bit 0x02 RST SCSI BUS Reset
1581 Generally SCSI targets do not reset the SCSI BUS, although any
1584 SCSI parity error detected.
1587 On a faulty SCSI BUS, any error condition among SGE (0x08), UDC (0x04) and
1588 PAR (0x01) may be detected by the chip. If your SCSI system sometimes
1589 encounters such error conditions, especially SCSI GROSS ERROR, then a SCSI
1596 This register reflects the state of the SCSI control lines the
1600 Actual value of control lines on the SCSI BUS.
1603 Actual value of data lines on the SCSI BUS.
1605 Field G : SXFER SCSI Transfer
1614 SCSI standards, chip cores functionnals and internal driver data structures.
1627 SCSI-2 mode.
1630 1 Mega-transfers/second means 1 MB/s with 8 bits SCSI and 2 MB/s with
1631 Wide16 SCSI.
1633 16.1 Synchronous timings for 53C895, 53C875 and 53C860 SCSI controllers
1721 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers