Orange Pi5 kernel

Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards

3 Commits   0 Branches   0 Tags
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300    1) .. SPDX-License-Identifier: GPL-2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300    2) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300    3) =================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300    4) The Linux NCR53C8XX/SYM53C8XX drivers README file
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300    5) =================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300    6) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300    7) Written by Gerard Roudier <groudier@free.fr>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300    8) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300    9) 21 Rue Carnot
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   10) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   11) 95170 DEUIL LA BARRE - FRANCE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   12) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   13) 29 May 1999
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   14) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   15) .. Contents:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   16) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   17)    1.  Introduction
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   18)    2.  Supported chips and SCSI features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   19)    3.  Advantages of the enhanced 896 driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   20)          3.1 Optimized SCSI SCRIPTS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   21)          3.2 New features of the SYM53C896 (64 bit PCI dual LVD SCSI controller)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   22)    4.  Memory mapped I/O versus normal I/O
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   23)    5.  Tagged command queueing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   24)    6.  Parity checking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   25)    7.  Profiling information
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   26)    8.  Control commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   27)          8.1  Set minimum synchronous period
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   28)          8.2  Set wide size
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   29)          8.3  Set maximum number of concurrent tagged commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   30)          8.4  Set order type for tagged command
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   31)          8.5  Set debug mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   32)          8.6  Clear profile counters
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   33)          8.7  Set flag (no_disc)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   34)          8.8  Set verbose level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   35)          8.9  Reset all logical units of a target
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   36)          8.10 Abort all tasks of all logical units of a target
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   37)    9.  Configuration parameters
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   38)    10. Boot setup commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   39)          10.1 Syntax
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   40)          10.2 Available arguments
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   41)                 10.2.1  Master parity checking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   42)                 10.2.2  Scsi parity checking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   43)                 10.2.3  Scsi disconnections
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   44)                 10.2.4  Special features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   45)                 10.2.5  Ultra SCSI support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   46)                 10.2.6  Default number of tagged commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   47)                 10.2.7  Default synchronous period factor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   48)                 10.2.8  Negotiate synchronous with all devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   49)                 10.2.9  Verbosity level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   50)                 10.2.10 Debug mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   51)                 10.2.11 Burst max
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   52)                 10.2.12 LED support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   53)                 10.2.13 Max wide
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   54)                 10.2.14 Differential mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   55)                 10.2.15 IRQ mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   56)                 10.2.16 Reverse probe
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   57)                 10.2.17 Fix up PCI configuration space
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   58)                 10.2.18 Serial NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   59)                 10.2.19 Check SCSI BUS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   60)                 10.2.20 Exclude a host from being attached
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   61)                 10.2.21 Suggest a default SCSI id for hosts
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   62)                 10.2.22 Enable use of IMMEDIATE ARBITRATION
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   63)          10.3 Advised boot setup commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   64)          10.4 PCI configuration fix-up boot option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   65)          10.5 Serial NVRAM support boot option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   66)          10.6 SCSI BUS checking boot option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   67)          10.7 IMMEDIATE ARBITRATION boot option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   68)    11. Some constants and flags of the ncr53c8xx.h header file
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   69)    12. Installation
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   70)    13. Architecture dependent features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   71)    14. Known problems
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   72)          14.1 Tagged commands with Iomega Jaz device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   73)          14.2 Device names change when another controller is added
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   74)          14.3 Using only 8 bit devices with a WIDE SCSI controller.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   75)          14.4 Possible data corruption during a Memory Write and Invalidate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   76)          14.5 IRQ sharing problems
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   77)    15. SCSI problem troubleshooting
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   78)          15.1 Problem tracking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   79)          15.2 Understanding hardware error reports
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   80)    16. Synchronous transfer negotiation tables
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   81)          16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   82)          16.2 Synchronous timings for fast SCSI-2 53C8XX controllers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   83)    17. Serial NVRAM support (by Richard Waltham)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   84)          17.1 Features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   85)          17.2 Symbios NVRAM layout
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   86)          17.3 Tekram  NVRAM layout
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   87)    18. Support for Big Endian
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   88)          18.1 Big Endian CPU
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   89)          18.2 NCR chip in Big Endian mode of operations
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   90) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   91) 1. Introduction
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   92) ===============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   93) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   94) The initial Linux ncr53c8xx driver has been a port of the ncr driver from
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   95) FreeBSD that has been achieved in November 1995 by:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   96) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   97) 	- Gerard Roudier              <groudier@free.fr>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   98) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   99) The original driver has been written for 386bsd and FreeBSD by:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  100) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  101)         - Wolfgang Stanglmeier        <wolf@cologne.de>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  102)         - Stefan Esser                <se@mi.Uni-Koeln.de>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  103) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  104) It is now available as a bundle of 2 drivers:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  105) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  106) - ncr53c8xx generic driver that supports all the SYM53C8XX family including
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  107)   the earliest 810 rev. 1, the latest 896 (2 channel LVD SCSI controller) and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  108)   the new 895A (1 channel LVD SCSI controller).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  109) - sym53c8xx enhanced driver (a.k.a. 896 drivers) that drops support of oldest
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  110)   chips in order to gain advantage of new features, as LOAD/STORE instructions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  111)   available since the 810A and hardware phase mismatch available with the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  112)   896 and the 895A.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  113) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  114) You can find technical information about the NCR 8xx family in the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  115) PCI-HOWTO written by Michael Will and in the SCSI-HOWTO written by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  116) Drew Eckhardt.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  117) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  118) Information about new chips is available at LSILOGIC web server:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  119) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  120)           - http://www.lsilogic.com/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  121) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  122) SCSI standard documentations are available at SYMBIOS ftp server:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  123) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  124)           - ftp://ftp.symbios.com/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  125) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  126) Useful SCSI tools written by Eric Youngdale are available at tsx-11:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  127) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  128)           - ftp://tsx-11.mit.edu/pub/linux/ALPHA/scsi/scsiinfo-X.Y.tar.gz
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  129)           - ftp://tsx-11.mit.edu/pub/linux/ALPHA/scsi/scsidev-X.Y.tar.gz
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  130) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  131) These tools are not ALPHA but quite clean and work quite well.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  132) It is essential you have the 'scsiinfo' package.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  133) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  134) This short documentation describes the features of the generic and enhanced
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  135) drivers, configuration parameters and control commands available through
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  136) the proc SCSI file system read / write operations.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  137) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  138) This driver has been tested OK with linux/i386, Linux/Alpha and Linux/PPC.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  139) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  140) Latest driver version and patches are available at:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  141) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  142)           - ftp://ftp.tux.org/pub/people/gerard-roudier
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  143) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  144) or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  145) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  146)           - ftp://ftp.symbios.com/mirror/ftp.tux.org/pub/tux/roudier/drivers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  147) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  148) I am not a native speaker of English and there are probably lots of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  149) mistakes in this README file. Any help will be welcome.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  150) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  151) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  152) 2. Supported chips and SCSI features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  153) ====================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  154) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  155) The following features are supported for all chips:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  156) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  157) 	- Synchronous negotiation
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  158) 	- Disconnection
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  159) 	- Tagged command queuing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  160) 	- SCSI parity checking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  161) 	- Master parity checking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  162) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  163) "Wide negotiation" is supported for chips that allow it.  The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  164) following table shows some characteristics of NCR 8xx family chips
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  165) and what drivers support them.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  166) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  167) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  168) |        |           |     |           |            |Supported by|Supported by|
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  169) |        |On board   |     |           |            |the generic |the enhanced|
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  170) |Chip    |SDMS BIOS  |Wide |SCSI std.  | Max. sync  |driver      |driver      |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  171) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  172) |810     |  N        | N   |  FAST10   | 10 MB/s    |    Y       |    N       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  173) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  174) |810A    |  N        | N   |  FAST10   | 10 MB/s    |    Y       |    Y       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  175) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  176) |815     |  Y        | N   |  FAST10   | 10 MB/s    |    Y       |    N       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  177) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  178) |825     |  Y        | Y   |  FAST10   | 20 MB/s    |    Y       |    N       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  179) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  180) |825A    |  Y        | Y   |  FAST10   | 20 MB/s    |    Y       |    Y       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  181) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  182) |860     |  N        | N   |  FAST20   | 20 MB/s    |    Y       |    Y       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  183) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  184) |875     |  Y        | Y   |  FAST20   | 40 MB/s    |    Y       |    Y       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  185) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  186) |876     |  Y        | Y   |  FAST20   | 40 MB/s    |    Y       |    Y       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  187) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  188) |895     |  Y        | Y   |  FAST40   | 80 MB/s    |    Y       |    Y       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  189) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  190) |895A    |  Y        | Y   |  FAST40   | 80 MB/s    |    Y       |    Y       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  191) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  192) |896     |  Y        | Y   |  FAST40   | 80 MB/s    |    Y       |    Y       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  193) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  194) |897     |  Y        | Y   |  FAST40   | 80 MB/s    |    Y       |    Y       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  195) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  196) |1510D   |  Y        | Y   |  FAST40   | 80 MB/s    |    Y       |    Y       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  197) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  198) |1010    |  Y        | Y   |  FAST80   |160 MB/s    |    N       |    Y       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  199) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  200) |1010_66 |  Y        | Y   |  FAST80   |160 MB/s    |    N       |    Y       |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  201) |[1]_    |           |     |           |            |            |            |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  202) +--------+-----------+-----+-----------+------------+------------+------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  203) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  204) .. [1] Chip supports 33MHz and 66MHz PCI buses.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  205) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  206) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  207) Summary of other supported features:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  208) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  209) :Module:                allow to load the driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  210) :Memory mapped I/O:     increases performance
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  211) :Profiling information: read operations from the proc SCSI file system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  212) :Control commands:      write operations to the proc SCSI file system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  213) :Debugging information: written to syslog (expert only)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  214) :Serial NVRAM:          Symbios and Tekram formats
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  215) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  216) - Scatter / gather
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  217) - Shared interrupt
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  218) - Boot setup commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  219) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  220) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  221) 3. Advantages of the enhanced 896 driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  222) ========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  223) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  224) 3.1 Optimized SCSI SCRIPTS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  225) --------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  226) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  227) The 810A, 825A, 875, 895, 896 and 895A support new SCSI SCRIPTS instructions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  228) named LOAD and STORE that allow to move up to 1 DWORD from/to an IO register
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  229) to/from memory much faster that the MOVE MEMORY instruction that is supported
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  230) by the 53c7xx and 53c8xx family.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  231) The LOAD/STORE instructions support absolute and DSA relative addressing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  232) modes.  The SCSI SCRIPTS had been entirely rewritten using LOAD/STORE instead
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  233) of MOVE MEMORY instructions.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  234) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  235) 3.2 New features of the SYM53C896 (64 bit PCI dual LVD SCSI controller)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  236) -----------------------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  237) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  238) The 896 and the 895A allows handling of the phase mismatch context from
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  239) SCRIPTS (avoids the phase mismatch interrupt that stops the SCSI processor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  240) until the C code has saved the context of the transfer).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  241) Implementing this without using LOAD/STORE instructions would be painful
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  242) and I didn't even want to try it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  243) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  244) The 896 chip supports 64 bit PCI transactions and addressing, while the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  245) 895A supports 32 bit PCI transactions and 64 bit addressing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  246) The SCRIPTS processor of these chips is not true 64 bit, but uses segment
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  247) registers for bit 32-63. Another interesting feature is that LOAD/STORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  248) instructions that address the on-chip RAM (8k) remain internal to the chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  249) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  250) Due to the use of LOAD/STORE SCRIPTS instructions, this driver does not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  251) support the following chips:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  252) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  253) - SYM53C810 revision < 0x10 (16)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  254) - SYM53C815 all revisions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  255) - SYM53C825 revision < 0x10 (16)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  256) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  257) 4. Memory mapped I/O versus normal I/O
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  258) ======================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  259) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  260) Memory mapped I/O has less latency than normal I/O.  Since
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  261) linux-1.3.x, memory mapped I/O is used rather than normal I/O.  Memory
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  262) mapped I/O seems to work fine on most hardware configurations, but
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  263) some poorly designed motherboards may break this feature.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  264) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  265) The configuration option CONFIG_SCSI_NCR53C8XX_IOMAPPED forces the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  266) driver to use normal I/O in all cases.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  267) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  268) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  269) 5. Tagged command queueing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  270) ==========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  271) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  272) Queuing more than 1 command at a time to a device allows it to perform
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  273) optimizations based on actual head positions and its mechanical
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  274) characteristics. This feature may also reduce average command latency.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  275) In order to really gain advantage of this feature, devices must have
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  276) a reasonable cache size (No miracle is to be expected for a low-end
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  277) hard disk with 128 KB or less).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  278) Some known SCSI devices do not properly support tagged command queuing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  279) Generally, firmware revisions that fix this kind of problems are available
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  280) at respective vendor web/ftp sites.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  281) All I can say is that the hard disks I use on my machines behave well with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  282) this driver with tagged command queuing enabled:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  283) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  284) - IBM S12 0662
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  285) - Conner 1080S
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  286) - Quantum Atlas I
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  287) - Quantum Atlas II
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  288) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  289) If your controller has NVRAM, you can configure this feature per target
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  290) from the user setup tool. The Tekram Setup program allows to tune the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  291) maximum number of queued commands up to 32. The Symbios Setup only allows
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  292) to enable or disable this feature.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  293) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  294) The maximum number of simultaneous tagged commands queued to a device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  295) is currently set to 8 by default.  This value is suitable for most SCSI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  296) disks.  With large SCSI disks (>= 2GB, cache >= 512KB, average seek time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  297) <= 10 ms), using a larger value may give better performances.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  298) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  299) The sym53c8xx driver supports up to 255 commands per device, and the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  300) generic ncr53c8xx driver supports up to 64, but using more than 32 is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  301) generally not worth-while, unless you are using a very large disk or disk
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  302) array. It is noticeable that most of recent hard disks seem not to accept
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  303) more than 64 simultaneous commands. So, using more than 64 queued commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  304) is probably just resource wasting.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  305) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  306) If your controller does not have NVRAM or if it is managed by the SDMS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  307) BIOS/SETUP, you can configure tagged queueing feature and device queue
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  308) depths from the boot command-line. For example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  309) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  310)   ncr53c8xx=tags:4/t2t3q15-t4q7/t1u0q32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  311) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  312) will set tagged commands queue depths as follow:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  313) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  314) - target 2  all luns  on controller 0 --> 15
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  315) - target 3  all luns  on controller 0 --> 15
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  316) - target 4  all luns  on controller 0 -->  7
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  317) - target 1  lun 0     on controller 1 --> 32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  318) - all other target/lun                -->  4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  319) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  320) In some special conditions, some SCSI disk firmwares may return a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  321) QUEUE FULL status for a SCSI command. This behaviour is managed by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  322) driver using the following heuristic:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  323) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  324) - Each time a QUEUE FULL status is returned, tagged queue depth is reduced
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  325)   to the actual number of disconnected commands.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  326) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  327) - Every 1000 successfully completed SCSI commands, if allowed by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  328)   current limit, the maximum number of queueable commands is incremented.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  329) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  330) Since QUEUE FULL status reception and handling is resource wasting, the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  331) driver notifies by default this problem to user by indicating the actual
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  332) number of commands used and their status, as well as its decision on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  333) device queue depth change.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  334) The heuristic used by the driver in handling QUEUE FULL ensures that the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  335) impact on performances is not too bad. You can get rid of the messages by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  336) setting verbose level to zero, as follow:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  337) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  338) 1st method:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  339) 	    boot your system using 'ncr53c8xx=verb:0' option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  340) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  341) 2nd method:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  342) 	    apply "setverbose 0" control command to the proc fs entry
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  343)             corresponding to your controller after boot-up.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  344) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  345) 6. Parity checking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  346) ==================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  347) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  348) The driver supports SCSI parity checking and PCI bus master parity
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  349) checking.  These features must be enabled in order to ensure safe data
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  350) transfers.  However, some flawed devices or mother boards will have
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  351) problems with parity. You can disable either PCI parity or SCSI parity
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  352) checking by entering appropriate options from the boot command line.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  353) (See 10: Boot setup commands).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  354) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  355) 7. Profiling information
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  356) ========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  357) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  358) Profiling information is available through the proc SCSI file system.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  359) Since gathering profiling information may impact performances, this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  360) feature is disabled by default and requires a compilation configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  361) option to be set to Y.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  362) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  363) The device associated with a host has the following pathname::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  364) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  365)           /proc/scsi/ncr53c8xx/N     (N=0,1,2 ....)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  366) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  367) Generally, only 1 board is used on hardware configuration, and that device is::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  368) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  369)           /proc/scsi/ncr53c8xx/0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  370) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  371) However, if the driver has been made as module, the number of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  372) hosts is incremented each time the driver is loaded.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  373) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  374) In order to display profiling information, just enter::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  375) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  376)          cat /proc/scsi/ncr53c8xx/0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  377) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  378) and you will get something like the following text::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  379) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  380)     General information:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  381)     Chip NCR53C810, device id 0x1, revision id 0x2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  382)     IO port address 0x6000, IRQ number 10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  383)     Using memory mapped IO at virtual address 0x282c000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  384)     Synchronous transfer period 25, max commands per lun 4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  385)     Profiling information:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  386)     num_trans    = 18014
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  387)     num_kbytes   = 671314
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  388)     num_disc     = 25763
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  389)     num_break    = 1673
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  390)     num_int      = 1685
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  391)     num_fly      = 18038
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  392)     ms_setup     = 4940
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  393)     ms_data      = 369940
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  394)     ms_disc      = 183090
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  395)     ms_post      = 1320
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  396) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  397) General information is easy to understand. The device ID and the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  398) revision ID identify the SCSI chip as follows:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  399) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  400) ======= ============= ===========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  401) Chip    Device id     Revision Id
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  402) ======= ============= ===========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  403) 810       0x1            <  0x10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  404) 810A      0x1            >= 0x10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  405) 815       0x4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  406) 825       0x3            <  0x10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  407) 860       0x6
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  408) 825A      0x3            >= 0x10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  409) 875       0xf
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  410) 895       0xc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  411) ======= ============= ===========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  412) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  413) The profiling information is updated upon completion of SCSI commands.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  414) A data structure is allocated and zeroed when the host adapter is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  415) attached. So, if the driver is a module, the profile counters are
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  416) cleared each time the driver is loaded.  The "clearprof" command
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  417) allows you to clear these counters at any time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  418) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  419) The following counters are available:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  420) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  421) ("num" prefix means "number of",
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  422) "ms" means milli-seconds)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  423) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  424) num_trans
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  425) 	Number of completed commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  426) 	Example above: 18014 completed commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  427) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  428) num_kbytes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  429) 	Number of kbytes transferred
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  430) 	Example above: 671 MB transferred
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  431) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  432) num_disc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  433) 	Number of SCSI disconnections
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  434) 	Example above: 25763 SCSI disconnections
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  435) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  436) num_break
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  437) 	number of script interruptions (phase mismatch)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  438) 	Example above: 1673 script interruptions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  439) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  440) num_int
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  441) 	Number of interrupts other than "on the fly"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  442) 	Example above: 1685 interruptions not "on the fly"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  443) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  444) num_fly
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  445) 	Number of interrupts "on the fly"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  446) 	Example above: 18038 interruptions "on the fly"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  447) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  448) ms_setup
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  449) 	Elapsed time for SCSI commands setups
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  450) 	Example above: 4.94 seconds
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  451) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  452) ms_data
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  453) 	Elapsed time for data transfers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  454) 	Example above: 369.94 seconds spent for data transfer
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  455) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  456) ms_disc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  457) 	Elapsed time for SCSI disconnections
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  458) 	Example above: 183.09 seconds spent disconnected
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  459) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  460) ms_post
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  461) 	Elapsed time for command post processing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  462) 	(time from SCSI status get to command completion call)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  463) 	Example above: 1.32 seconds spent for post processing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  464) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  465) Due to the 1/100 second tick of the system clock, "ms_post" time may
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  466) be wrong.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  467) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  468) In the example above, we got 18038 interrupts "on the fly" and only
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  469) 1673 script breaks generally due to disconnections inside a segment
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  470) of the scatter list.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  471) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  472) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  473) 8. Control commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  474) ===================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  475) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  476) Control commands can be sent to the driver with write operations to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  477) the proc SCSI file system. The generic command syntax is the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  478) following::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  479) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  480)       echo "<verb> <parameters>" >/proc/scsi/ncr53c8xx/0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  481)       (assumes controller number is 0)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  482) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  483) Using "all" for "<target>" parameter with the commands below will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  484) apply to all targets of the SCSI chain (except the controller).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  485) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  486) Available commands:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  487) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  488) 8.1 Set minimum synchronous period factor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  489) -----------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  490) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  491)     setsync <target> <period factor>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  492) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  493)     :target:   target number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  494)     :period:   minimum synchronous period.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  495)                Maximum speed = 1000/(4*period factor) except for special
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  496)                cases below.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  497) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  498)     Specify a period of 255, to force asynchronous transfer mode.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  499) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  500)       - 10 means 25 nano-seconds synchronous period
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  501)       - 11 means 30 nano-seconds synchronous period
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  502)       - 12 means 50 nano-seconds synchronous period
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  503) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  504) 8.2 Set wide size
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  505) -----------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  506) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  507)     setwide <target> <size>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  508) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  509)     :target:   target number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  510)     :size:     0=8 bits, 1=16bits
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  511) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  512) 8.3 Set maximum number of concurrent tagged commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  513) ----------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  514) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  515)     settags <target> <tags>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  516) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  517)     :target:   target number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  518)     :tags:     number of concurrent tagged commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  519)                must not be greater than SCSI_NCR_MAX_TAGS (default: 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  520) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  521) 8.4 Set order type for tagged command
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  522) -------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  523) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  524)     setorder <order>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  525) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  526)     :order:    3 possible values:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  527) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  528)                simple:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  529) 			use SIMPLE TAG for all operations (read and write)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  530) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  531)                ordered:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  532) 			use ORDERED TAG for all operations
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  533) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  534)                default:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  535) 			use default tag type,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  536)                         SIMPLE  TAG for read  operations
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  537)                         ORDERED TAG for write operations
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  538) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  539) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  540) 8.5 Set debug mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  541) ------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  542) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  543)     setdebug <list of debug flags>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  544) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  545)     Available debug flags:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  546) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  547) 	======== ========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  548)         alloc    print info about memory allocations (ccb, lcb)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  549)         queue    print info about insertions into the command start queue
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  550)         result   print sense data on CHECK CONDITION status
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  551)         scatter  print info about the scatter process
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  552)         scripts  print info about the script binding process
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  553) 	tiny     print minimal debugging information
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  554) 	timing   print timing information of the NCR chip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  555) 	nego     print information about SCSI negotiations
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  556) 	phase    print information on script interruptions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  557) 	======== ========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  558) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  559)     Use "setdebug" with no argument to reset debug flags.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  560) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  561) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  562) 8.6 Clear profile counters
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  563) --------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  564) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  565)     clearprof
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  566) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  567)     The profile counters are automatically cleared when the amount of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  568)     data transferred reaches 1000 GB in order to avoid overflow.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  569)     The "clearprof" command allows you to clear these counters at any time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  570) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  571) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  572) 8.7 Set flag (no_disc)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  573) ----------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  574) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  575)     setflag <target> <flag>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  576) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  577)     target:    target number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  578) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  579)     For the moment, only one flag is available:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  580) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  581)         no_disc:   not allow target to disconnect.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  582) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  583)     Do not specify any flag in order to reset the flag. For example:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  584) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  585)     setflag 4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  586)       will reset no_disc flag for target 4, so will allow it disconnections.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  587) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  588)     setflag all
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  589)       will allow disconnection for all devices on the SCSI bus.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  590) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  591) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  592) 8.8 Set verbose level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  593) ---------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  594) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  595)     setverbose #level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  596) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  597)     The driver default verbose level is 1. This command allows to change
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  598)     th driver verbose level after boot-up.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  599) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  600) 8.9 Reset all logical units of a target
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  601) ---------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  602) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  603)     resetdev <target>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  604) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  605)     :target:   target number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  606) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  607)     The driver will try to send a BUS DEVICE RESET message to the target.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  608)     (Only supported by the SYM53C8XX driver and provided for test purpose)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  609) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  610) 8.10 Abort all tasks of all logical units of a target
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  611) -----------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  612) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  613)     cleardev <target>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  614) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  615)     :target:   target number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  616) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  617)     The driver will try to send a ABORT message to all the logical units
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  618)     of the target.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  619) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  620)     (Only supported by the SYM53C8XX driver and provided for test purpose)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  621) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  622) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  623) 9. Configuration parameters
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  624) ===========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  625) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  626) If the firmware of all your devices is perfect enough, all the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  627) features supported by the driver can be enabled at start-up.  However,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  628) if only one has a flaw for some SCSI feature, you can disable the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  629) support by the driver of this feature at linux start-up and enable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  630) this feature after boot-up only for devices that support it safely.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  631) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  632) CONFIG_SCSI_NCR53C8XX_IOMAPPED       (default answer: n)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  633)     Answer "y" if you suspect your mother board to not allow memory mapped I/O.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  634) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  635)     May slow down performance a little.  This option is required by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  636)     Linux/PPC and is used no matter what you select here.  Linux/PPC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  637)     suffers no performance loss with this option since all IO is memory
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  638)     mapped anyway.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  639) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  640) CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS    (default answer: 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  641)     Default tagged command queue depth.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  642) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  643) CONFIG_SCSI_NCR53C8XX_MAX_TAGS         (default answer: 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  644)     This option allows you to specify the maximum number of tagged commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  645)     that can be queued to a device. The maximum supported value is 32.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  646) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  647) CONFIG_SCSI_NCR53C8XX_SYNC            (default answer: 5)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  648)     This option allows you to specify the frequency in MHz the driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  649)     will use at boot time for synchronous data transfer negotiations.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  650)     This frequency can be changed later with the "setsync" control command.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  651)     0 means "asynchronous data transfers".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  652) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  653) CONFIG_SCSI_NCR53C8XX_FORCE_SYNC_NEGO (default answer: n)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  654)     Force synchronous negotiation for all SCSI-2 devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  655) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  656)     Some SCSI-2 devices do not report this feature in byte 7 of inquiry
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  657)     response but do support it properly (TAMARACK scanners for example).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  658) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  659) CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT   (default and only reasonable answer: n)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  660)     If you suspect a device of yours does not properly support disconnections,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  661)     you can answer "y". Then, all SCSI devices will never disconnect the bus
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  662)     even while performing long SCSI operations.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  663) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  664) CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  665)     Genuine SYMBIOS boards use GPIO0 in output for controller LED and GPIO3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  666)     bit as a flag indicating singled-ended/differential interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  667)     If all the boards of your system are genuine SYMBIOS boards or use
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  668)     BIOS and drivers from SYMBIOS, you would want to enable this option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  669) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  670)     This option must NOT be enabled if your system has at least one 53C8XX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  671)     based scsi board with a vendor-specific BIOS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  672)     For example, Tekram DC-390/U, DC-390/W and DC-390/F scsi controllers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  673)     use a vendor-specific BIOS and are known to not use SYMBIOS compatible
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  674)     GPIO wiring. So, this option must not be enabled if your system has
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  675)     such a board installed.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  676) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  677) CONFIG_SCSI_NCR53C8XX_NVRAM_DETECT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  678)     Enable support for reading the serial NVRAM data on Symbios and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  679)     some Symbios compatible cards, and Tekram DC390W/U/F cards. Useful for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  680)     systems with more than one Symbios compatible controller where at least
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  681)     one has a serial NVRAM, or for a system with a mixture of Symbios and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  682)     Tekram cards. Enables setting the boot order of host adaptors
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  683)     to something other than the default order or "reverse probe" order.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  684)     Also enables Symbios and Tekram cards to be distinguished so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  685)     CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT may be set in a system with a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  686)     mixture of Symbios and Tekram cards so the Symbios cards can make use of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  687)     the full range of Symbios features, differential, led pin, without
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  688)     causing problems for the Tekram card(s).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  689) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  690) 10. Boot setup commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  691) =======================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  692) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  693) 10.1 Syntax
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  694) -----------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  695) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  696) Setup commands can be passed to the driver either at boot time or as a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  697) string variable using 'insmod'.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  698) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  699) A boot setup command for the ncr53c8xx (sym53c8xx) driver begins with the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  700) driver name "ncr53c8xx="(sym53c8xx). The kernel syntax parser then expects
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  701) an optional list of integers separated with comma followed by an optional
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  702) list of comma-separated strings. Example of boot setup command under lilo
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  703) prompt::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  704) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  705)     lilo: linux root=/dev/hda2 ncr53c8xx=tags:4,sync:10,debug:0x200
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  706) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  707) - enable tagged commands, up to 4 tagged commands queued.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  708) - set synchronous negotiation speed to 10 Mega-transfers / second.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  709) - set DEBUG_NEGO flag.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  710) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  711) Since comma seems not to be allowed when defining a string variable using
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  712) 'insmod', the driver also accepts <space> as option separator.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  713) The following command will install driver module with the same options as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  714) above::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  715) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  716)     insmod ncr53c8xx.o ncr53c8xx="tags:4 sync:10 debug:0x200"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  717) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  718) For the moment, the integer list of arguments is discarded by the driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  719) It will be used in the future in order to allow a per controller setup.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  720) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  721) Each string argument must be specified as "keyword:value". Only lower-case
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  722) characters and digits are allowed.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  723) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  724) In a system that contains multiple 53C8xx adapters insmod will install the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  725) specified driver on each adapter. To exclude a chip use the 'excl' keyword.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  726) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  727) The sequence of commands::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  728) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  729)     insmod sym53c8xx sym53c8xx=excl:0x1400
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  730)     insmod ncr53c8xx
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  731) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  732) installs the sym53c8xx driver on all adapters except the one at IO port
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  733) address 0x1400 and then installs the ncr53c8xx driver to the adapter at IO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  734) port address 0x1400.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  735) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  736) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  737) 10.2 Available arguments
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  738) ------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  739) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  740) 10.2.1  Master parity checking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  741) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  742) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  743) 	======     ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  744)         mpar:y     enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  745)         mpar:n     disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  746) 	======     ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  747) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  748) 10.2.2  Scsi parity checking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  749) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  750) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  751) 	======     ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  752)         spar:y     enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  753)         spar:n     disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  754) 	======     ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  755) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  756) 10.2.3  Scsi disconnections
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  757) ^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  758) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  759) 	======     ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  760)         disc:y     enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  761)         disc:n     disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  762) 	======     ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  763) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  764) 10.2.4  Special features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  765) ^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  766) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  767)    Only apply to 810A, 825A, 860, 875 and 895 controllers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  768)    Have no effect with other ones.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  769) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  770) 	=======    =================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  771)         specf:y    (or 1) enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  772)         specf:n    (or 0) disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  773)         specf:3           enabled except Memory Write And Invalidate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  774) 	=======    =================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  775) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  776)    The default driver setup is 'specf:3'. As a consequence, option 'specf:y'
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  777)    must be specified in the boot setup command to enable Memory Write And
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  778)    Invalidate.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  779) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  780) 10.2.5  Ultra SCSI support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  781) ^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  782) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  783)    Only apply to 860, 875, 895, 895a, 896, 1010 and 1010_66 controllers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  784)    Have no effect with other ones.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  785) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  786) 	=======    ========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  787)         ultra:n    All ultra speeds enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  788)         ultra:2    Ultra2 enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  789)         ultra:1    Ultra enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  790)         ultra:0    Ultra speeds disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  791) 	=======    ========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  792) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  793) 10.2.6  Default number of tagged commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  794) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  795) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  796) 	======================= ===============================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  797)         tags:0     (or tags:1 ) tagged command queuing disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  798)         tags:#tags (#tags  > 1) tagged command queuing enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  799) 	======================= ===============================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  800) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  801)   #tags will be truncated to the max queued commands configuration parameter.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  802)   This option also allows to specify a command queue depth for each device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  803)   that support tagged command queueing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  804) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  805)   Example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  806) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  807)       ncr53c8xx=tags:10/t2t3q16-t5q24/t1u2q32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  808) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  809)   will set devices queue depth as follow:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  810) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  811)       - controller #0 target #2 and target #3                  -> 16 commands,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  812)       - controller #0 target #5                                -> 24 commands,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  813)       - controller #1 target #1 logical unit #2                -> 32 commands,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  814)       - all other logical units (all targets, all controllers) -> 10 commands.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  815) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  816) 10.2.7  Default synchronous period factor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  817) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  818) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  819) ============ ========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  820) sync:255     disabled (asynchronous transfer mode)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  821) sync:#factor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  822) 	     ============     =======================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  823) 	     #factor = 10     Ultra-2 SCSI 40 Mega-transfers / second
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  824) 	     #factor = 11     Ultra-2 SCSI 33 Mega-transfers / second
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  825) 	     #factor < 25     Ultra   SCSI 20 Mega-transfers / second
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  826) 	     #factor < 50     Fast    SCSI-2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  827) 	     ============     =======================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  828) ============ ========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  829) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  830)   In all cases, the driver will use the minimum transfer period supported by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  831)   controllers according to NCR53C8XX chip type.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  832) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  833) 10.2.8  Negotiate synchronous with all devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  834) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  835)         (force sync nego)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  836) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  837)         =====      =========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  838)         fsn:y      enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  839)         fsn:n      disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  840)         =====      =========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  841) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  842) 10.2.9  Verbosity level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  843) ^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  844) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  845)         ======     =========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  846)         verb:0     minimal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  847)         verb:1     normal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  848)         verb:2     too much
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  849)         ======     =========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  850) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  851) 10.2.10 Debug mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  852) ^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  853) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  854) ========   ==================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  855) debug:0    clear debug flags
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  856) debug:#x   set debug flags
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  857) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  858) 	    #x is an integer value combining the following power-of-2 values:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  859) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  860) 	    =============  ======
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  861) 	    DEBUG_ALLOC       0x1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  862) 	    DEBUG_PHASE       0x2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  863) 	    DEBUG_POLL        0x4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  864) 	    DEBUG_QUEUE       0x8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  865) 	    DEBUG_RESULT     0x10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  866) 	    DEBUG_SCATTER    0x20
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  867) 	    DEBUG_SCRIPT     0x40
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  868) 	    DEBUG_TINY       0x80
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  869) 	    DEBUG_TIMING    0x100
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  870) 	    DEBUG_NEGO      0x200
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  871) 	    DEBUG_TAGS      0x400
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  872) 	    DEBUG_FREEZE    0x800
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  873) 	    DEBUG_RESTART  0x1000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  874) 	    =============  ======
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  875) ========   ==================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  876) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  877)   You can play safely with DEBUG_NEGO. However, some of these flags may
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  878)   generate bunches of syslog messages.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  879) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  880) 10.2.11 Burst max
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  881) ^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  882) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  883) =========  ==================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  884) burst:0    burst disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  885) burst:255  get burst length from initial IO register settings.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  886) burst:#x   burst enabled (1<<#x burst transfers max)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  887) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  888) 	   #x is an integer value which is log base 2 of the burst transfers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  889) 	   max.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  890) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  891) 	   The NCR53C875 and NCR53C825A support up to 128 burst transfers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  892) 	   (#x = 7).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  893) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  894) 	   Other chips only support up to 16 (#x = 4).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  895) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  896) 	   This is a maximum value. The driver set the burst length according
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  897) 	   to chip and revision ids. By default the driver uses the maximum
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  898) 	   value supported by the chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  899) =========  ==================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  900) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  901) 10.2.12 LED support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  902) ^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  903) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  904)         =====      ===================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  905)         led:1      enable  LED support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  906)         led:0      disable LED support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  907)         =====      ===================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  908) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  909)   Donnot enable LED support if your scsi board does not use SDMS BIOS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  910)   (See 'Configuration parameters')
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  911) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  912) 10.2.13 Max wide
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  913) ^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  914) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  915)         ======     ===================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  916)         wide:1      wide scsi enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  917)         wide:0      wide scsi disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  918)         ======     ===================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  919) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  920)   Some scsi boards use a 875 (ultra wide) and only supply narrow connectors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  921)   If you have connected a wide device with a 50 pins to 68 pins cable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  922)   converter, any accepted wide negotiation will break further data transfers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  923)   In such a case, using "wide:0" in the bootup command will be helpful.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  924) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  925) 10.2.14 Differential mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  926) ^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  927) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  928) 	======	=================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  929)         diff:0	never set up diff mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  930)         diff:1	set up diff mode if BIOS set it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  931)         diff:2	always set up diff mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  932)         diff:3	set diff mode if GPIO3 is not set
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  933) 	======	=================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  934) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  935) 10.2.15 IRQ mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  936) ^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  937) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  938) 	=========  ========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  939)         irqm:0     always open drain
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  940)         irqm:1     same as initial settings (assumed BIOS settings)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  941)         irqm:2     always totem pole
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  942)         irqm:0x10  driver will not use IRQF_SHARED flag when requesting irq
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  943) 	=========  ========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  944) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  945)     (Bits 0x10 and 0x20 can be combined with hardware irq mode option)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  946) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  947) 10.2.16 Reverse probe
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  948) ^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  949) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  950) 	=========   ========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  951)         revprob:n   probe chip ids from the PCI configuration in this order:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  952)                     810, 815, 820, 860, 875, 885, 895, 896
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  953)         revprob:y   probe chip ids in the reverse order.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  954) 	=========   ========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  955) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  956) 10.2.17 Fix up PCI configuration space
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  957) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  958)         pcifix:<option bits>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  959) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  960)     Available option bits:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  961) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  962) 	===    ===============================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  963)         0x0    No attempt to fix PCI configuration space registers values.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  964)         0x1    Set PCI cache-line size register if not set.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  965)         0x2    Set write and invalidate bit in PCI command register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  966)         0x4    Increase if necessary PCI latency timer according to burst max.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  967) 	===    ===============================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  968) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  969)     Use 'pcifix:7' in order to allow the driver to fix up all PCI features.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  970) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  971) 10.2.18 Serial NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  972) ^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  973) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  974) 	=======     =========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  975)         nvram:n     do not look for serial NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  976)         nvram:y     test controllers for onboard serial NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  977) 	=======     =========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  978) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  979)         (alternate binary form)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  980)         mvram=<bits options>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  981) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  982)         ====   =================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  983)         0x01   look for NVRAM  (equivalent to nvram=y)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  984)         0x02   ignore NVRAM "Synchronous negotiation" parameters for all devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  985)         0x04   ignore NVRAM "Wide negotiation"  parameter for all devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  986)         0x08   ignore NVRAM "Scan at boot time" parameter for all devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  987)         0x80   also attach controllers set to OFF in the NVRAM (sym53c8xx only)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  988)         ====   =================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  989) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  990) 10.2.19 Check SCSI BUS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  991) ^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  992) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  993)         buschk:<option bits>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  994) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  995)     Available option bits:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  996) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  997)         ====   ================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  998)         0x0:   No check.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  999)         0x1:   Check and do not attach the controller on error.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1000)         0x2:   Check and just warn on error.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1001)         0x4:   Disable SCSI bus integrity checking.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1002)         ====   ================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1003) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1004) 10.2.20 Exclude a host from being attached
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1005) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1006) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1007)         excl=<io_address>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1008) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1009)     Prevent host at a given io address from being attached.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1010)     For example 'ncr53c8xx=excl:0xb400,excl:0xc000' indicate to the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1011)     ncr53c8xx driver not to attach hosts at address 0xb400 and 0xc000.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1012) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1013) 10.2.21 Suggest a default SCSI id for hosts
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1014) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1015) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1016) 	==========	==========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1017)         hostid:255	no id suggested.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1018)         hostid:#x	(0 < x < 7) x suggested for hosts SCSI id.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1019) 	==========	==========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1020) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1021)     If a host SCSI id is available from the NVRAM, the driver will ignore
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1022)     any value suggested as boot option. Otherwise, if a suggested value
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1023)     different from 255 has been supplied, it will use it. Otherwise, it will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1024)     try to deduce the value previously set in the hardware and use value
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1025)     7 if the hardware value is zero.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1026) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1027) 10.2.22 Enable use of IMMEDIATE ARBITRATION
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1028) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1029) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1030)         (only supported by the sym53c8xx driver. See 10.7 for more details)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1031) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1032) =======   =================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1033) iarb:0    do not use this feature.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1034) iarb:#x   use this feature according to bit fields as follow:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1035) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1036) 	  ========= =======================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1037) 	  bit 0 (1) enable IARB each time the initiator has been reselected
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1038) 		    when it arbitrated for the SCSI BUS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1039) 	  (#x >> 4) maximum number of successive settings of IARB if the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1040) 		    initiator win arbitration and it has other commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1041) 		    to send to a device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1042) 	  ========= =======================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1043) =======   =================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1044) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1045) Boot fail safe
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1046)     safe:y	load the following assumed fail safe initial setup
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1047) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1048)   ========================	======================	==========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1049)   master parity			disabled		mpar:n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1050)   scsi parity			enabled			spar:y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1051)   disconnections		not allowed		disc:n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1052)   special features		disabled		specf:n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1053)   ultra scsi			disabled		ultra:n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1054)   force sync negotiation	disabled		fsn:n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1055)   reverse probe			disabled		revprob:n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1056)   PCI fix up                    disabled                pcifix:0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1057)   serial NVRAM                  enabled                 nvram:y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1058)   verbosity level		2			verb:2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1059)   tagged command queuing	disabled		tags:0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1060)   synchronous negotiation	disabled		sync:255
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1061)   debug flags			none			debug:0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1062)   burst length			from BIOS settings	burst:255
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1063)   LED support			disabled		led:0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1064)   wide support			disabled		wide:0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1065)   settle time			10 seconds		settle:10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1066)   differential support		from BIOS settings	diff:1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1067)   irq mode			from BIOS settings	irqm:1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1068)   SCSI BUS check		do not attach on error	buschk:1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1069)   immediate arbitration		disabled		iarb:0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1070)   ========================	======================	==========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1071) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1072) 10.3 Advised boot setup commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1073) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1074) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1075) If the driver has been configured with default options, the equivalent
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1076) boot setup is::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1077) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1078)    ncr53c8xx=mpar:y,spar:y,disc:y,specf:3,fsn:n,ultra:2,fsn:n,revprob:n,verb:1\
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1079)              tags:0,sync:50,debug:0,burst:7,led:0,wide:1,settle:2,diff:0,irqm:0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1080) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1081) For an installation diskette or a safe but not fast system,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1082) boot setup can be::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1083) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1084)     ncr53c8xx=safe:y,mpar:y,disc:y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1085)     ncr53c8xx=safe:y,disc:y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1086)     ncr53c8xx=safe:y,mpar:y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1087)     ncr53c8xx=safe:y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1088) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1089) My personal system works flawlessly with the following equivalent setup::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1090) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1091)    ncr53c8xx=mpar:y,spar:y,disc:y,specf:1,fsn:n,ultra:2,fsn:n,revprob:n,verb:1\
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1092)              tags:32,sync:12,debug:0,burst:7,led:1,wide:1,settle:2,diff:0,irqm:0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1093) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1094) The driver prints its actual setup when verbosity level is 2. You can try
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1095) "ncr53c8xx=verb:2" to get the "static" setup of the driver, or add "verb:2"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1096) to your boot setup command in order to check the actual setup the driver is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1097) using.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1098) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1099) 10.4 PCI configuration fix-up boot option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1100) -----------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1101) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1102) pcifix:<option bits>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1103) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1104) Available option bits:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1105) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1106)     ===      =====================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1107)     0x1      Set PCI cache-line size register if not set.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1108)     0x2      Set write and invalidate bit in PCI command register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1109)     ===      =====================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1110) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1111) Use 'pcifix:3' in order to allow the driver to fix both PCI features.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1112) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1113) These options only apply to new SYMBIOS chips 810A, 825A, 860, 875
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1114) and 895 and are only supported for Pentium and 486 class processors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1115) Recent SYMBIOS 53C8XX scsi processors are able to use PCI read multiple
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1116) and PCI write and invalidate commands. These features require the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1117) cache line size register to be properly set in the PCI configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1118) space of the chips. On the other hand, chips will use PCI write and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1119) invalidate commands only if the corresponding bit is set to 1 in the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1120) PCI command register.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1121) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1122) Not all PCI bioses set the PCI cache line register and the PCI write and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1123) invalidate bit in the PCI configuration space of 53C8XX chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1124) Optimized PCI accesses may be broken for some PCI/memory controllers or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1125) make problems with some PCI boards.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1126) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1127) This fix-up worked flawlessly on my previous system.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1128) (MB Triton HX / 53C875 / 53C810A)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1129) I use these options at my own risks as you will do if you decide to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1130) use them too.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1131) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1132) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1133) 10.5 Serial NVRAM support boot option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1134) -------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1135) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1136) =======     =========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1137) nvram:n     do not look for serial NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1138) nvram:y     test controllers for onboard serial NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1139) =======     =========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1140) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1141) This option can also been entered as an hexadecimal value that allows
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1142) to control what information the driver will get from the NVRAM and what
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1143) information it will ignore.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1144) For details see '17. Serial NVRAM support'.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1145) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1146) When this option is enabled, the driver tries to detect all boards using
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1147) a Serial NVRAM. This memory is used to hold user set up parameters.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1148) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1149) The parameters the driver is able to get from the NVRAM depend on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1150) data format used, as follow:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1151) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1152) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1153) |                               |Tekram format     |Symbios format|
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1154) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1155) |General and host parameters    |                  |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1156) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1157) |  * Boot order                 |        N         |       Y      |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1158) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1159) |  * Host SCSI ID               |        Y         |       Y      |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1160) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1161) |  * SCSI parity checking       |        Y         |       Y      |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1162) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1163) |  * Verbose boot messages      |        N         |       Y      |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1164) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1165) |SCSI devices parameters                                          |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1166) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1167) |  * Synchronous transfer speed |        Y         |       Y      |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1168) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1169) |  * Wide 16 / Narrow           |        Y         |       Y      |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1170) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1171) |  * Tagged Command Queuing     |        Y         |       Y      |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1172) |    enabled                    |                  |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1173) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1174) |  * Disconnections enabled     |        Y         |       Y      |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1175) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1176) |  * Scan at boot time          |        N         |       Y      |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1177) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1178) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1179) In order to speed up the system boot, for each device configured without
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1180) the "scan at boot time" option, the driver forces an error on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1181) first TEST UNIT READY command received for this device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1182) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1183) Some SDMS BIOS revisions seem to be unable to boot cleanly with very fast
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1184) hard disks. In such a situation you cannot configure the NVRAM with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1185) optimized parameters value.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1186) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1187) The 'nvram' boot option can be entered in hexadecimal form in order
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1188) to ignore some options configured in the NVRAM, as follow:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1189) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1190) mvram=<bits options>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1191) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1192)       ====   =================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1193)       0x01   look for NVRAM  (equivalent to nvram=y)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1194)       0x02   ignore NVRAM "Synchronous negotiation" parameters for all devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1195)       0x04   ignore NVRAM "Wide negotiation"  parameter for all devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1196)       0x08   ignore NVRAM "Scan at boot time" parameter for all devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1197)       0x80   also attach controllers set to OFF in the NVRAM (sym53c8xx only)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1198)       ====   =================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1199) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1200) Option 0x80 is only supported by the sym53c8xx driver and is disabled by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1201) default. Result is that, by default (option not set), the sym53c8xx driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1202) will not attach controllers set to OFF in the NVRAM.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1203) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1204) The ncr53c8xx always tries to attach all the controllers. Option 0x80 has
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1205) not been added to the ncr53c8xx driver, since it has been reported to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1206) confuse users who use this driver since a long time. If you desire a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1207) controller not to be attached by the ncr53c8xx driver at Linux boot, you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1208) must use the 'excl' driver boot option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1209) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1210) 10.6 SCSI BUS checking boot option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1211) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1212) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1213) When this option is set to a non-zero value, the driver checks SCSI lines
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1214) logic state, 100 micro-seconds after having asserted the SCSI RESET line.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1215) The driver just reads SCSI lines and checks all lines read FALSE except RESET.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1216) Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1217) RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1218) Unfortunately, the following common SCSI BUS problems are not detected:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1219) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1220) - Only 1 terminator installed.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1221) - Misplaced terminators.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1222) - Bad quality terminators.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1223) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1224) On the other hand, either bad cabling, broken devices, not conformant
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1225) devices, ... may cause a SCSI signal to be wrong when te driver reads it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1226) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1227) 10.7 IMMEDIATE ARBITRATION boot option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1228) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1229) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1230) This option is only supported by the SYM53C8XX driver (not by the NCR53C8XX).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1231) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1232) SYMBIOS 53C8XX chips are able to arbitrate for the SCSI BUS as soon as they
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1233) have detected an expected disconnection (BUS FREE PHASE). For this process
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1234) to be started, bit 1 of SCNTL1 IO register must be set when the chip is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1235) connected to the SCSI BUS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1236) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1237) When this feature has been enabled for the current connection, the chip has
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1238) every chance to win arbitration if only devices with lower priority are
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1239) competing for the SCSI BUS. By the way, when the chip is using SCSI id 7,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1240) then it will for sure win the next SCSI BUS arbitration.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1241) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1242) Since, there is no way to know what devices are trying to arbitrate for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1243) BUS, using this feature can be extremely unfair. So, you are not advised
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1244) to enable it, or at most enable this feature for the case the chip lost
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1245) the previous arbitration (boot option 'iarb:1').
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1246) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1247) This feature has the following advantages:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1248) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1249) a) Allow the initiator with ID 7 to win arbitration when it wants so.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1250) b) Overlap at least 4 micro-seconds of arbitration time with the execution
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1251)    of SCRIPTS that deal with the end of the current connection and that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1252)    starts the next job.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1253) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1254) Hmmm... But (a) may just prevent other devices from reselecting the initiator,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1255) and delay data transfers or status/completions, and (b) may just waste
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1256) SCSI BUS bandwidth if the SCRIPTS execution lasts more than 4 micro-seconds.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1257) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1258) The use of IARB needs the SCSI_NCR_IARB_SUPPORT option to have been defined
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1259) at compile time and the 'iarb' boot option to have been set to a non zero
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1260) value at boot time. It is not that useful for real work, but can be used
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1261) to stress SCSI devices or for some applications that can gain advantage of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1262) it. By the way, if you experience badnesses like 'unexpected disconnections',
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1263) 'bad reselections', etc... when using IARB on heavy IO load, you should not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1264) be surprised, because force-feeding anything and blocking its arse at the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1265) same time cannot work for a long time. :-))
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1266) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1267) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1268) 11. Some constants and flags of the ncr53c8xx.h header file
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1269) ===========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1270) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1271) Some of these are defined from the configuration parameters.  To
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1272) change other "defines", you must edit the header file.  Do that only
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1273) if you know what you are doing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1274) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1275) SCSI_NCR_SETUP_SPECIAL_FEATURES	(default: defined)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1276) 	If defined, the driver will enable some special features according
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1277) 	to chip and revision id.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1278) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1279)         For 810A, 860, 825A, 875 and 895 scsi chips, this option enables
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1280) 	support of features that reduce load of PCI bus and memory accesses
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1281) 	during  scsi transfer processing: burst op-code fetch, read multiple,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1282)         read line, prefetch, cache line, write and invalidate,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1283)         burst 128 (875 only), large dma fifo (875 only), offset 16 (875 only).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1284) 	Can be changed by the following boot setup command::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1285) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1286) 		ncr53c8xx=specf:n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1287) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1288) SCSI_NCR_IOMAPPED		(default: not defined)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1289) 	If defined, normal I/O is forced.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1290) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1291) SCSI_NCR_SHARE_IRQ		(default: defined)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1292) 	If defined, request shared IRQ.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1293) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1294) SCSI_NCR_MAX_TAGS		(default: 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1295) 	Maximum number of simultaneous tagged commands to a device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1296) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1297) 	Can be changed by "settags <target> <maxtags>"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1298) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1299) SCSI_NCR_SETUP_DEFAULT_SYNC     (default: 50)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1300) 	Transfer period factor the driver will use at boot time for synchronous
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1301) 	negotiation. 0 means asynchronous.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1302) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1303) 	Can be changed by "setsync <target> <period factor>"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1304) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1305) SCSI_NCR_SETUP_DEFAULT_TAGS     (default: 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1306) 	Default number of simultaneous tagged commands to a device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1307) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1308) 	< 1 means tagged command queuing disabled at start-up.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1309) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1310) SCSI_NCR_ALWAYS_SIMPLE_TAG	(default: defined)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1311) 	Use SIMPLE TAG for read and write commands.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1312) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1313) 	Can be changed by "setorder <ordered|simple|default>"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1314) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1315) SCSI_NCR_SETUP_DISCONNECTION	(default: defined)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1316) 	If defined, targets are allowed to disconnect.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1317) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1318) SCSI_NCR_SETUP_FORCE_SYNC_NEGO	(default: not defined)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1319) 	If defined, synchronous negotiation is tried for all SCSI-2 devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1320) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1321) 	Can be changed by "setsync <target> <period>"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1322) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1323) SCSI_NCR_SETUP_MASTER_PARITY	(default: defined)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1324) 	If defined, master parity checking is enabled.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1325) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1326) SCSI_NCR_SETUP_SCSI_PARITY	(default: defined)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1327) 	If defined, SCSI parity checking is enabled.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1328) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1329) SCSI_NCR_PROFILE_SUPPORT	(default: not defined)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1330) 	If defined, profiling information is gathered.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1331) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1332) SCSI_NCR_MAX_SCATTER		(default: 128)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1333) 	Scatter list size of the driver ccb.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1334) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1335) SCSI_NCR_MAX_TARGET		(default: 16)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1336) 	Max number of targets per host.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1337) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1338) SCSI_NCR_MAX_HOST		(default: 2)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1339) 	Max number of host controllers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1340) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1341) SCSI_NCR_SETTLE_TIME		(default: 2)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1342) 	Number of seconds the driver will wait after reset.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1343) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1344) SCSI_NCR_TIMEOUT_ALERT		(default: 3)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1345) 	If a pending command will time out after this amount of seconds,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1346) 	an ordered tag is used for the next command.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1347) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1348) 	Avoids timeouts for unordered tagged commands.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1349) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1350) SCSI_NCR_CAN_QUEUE		(default: 7*SCSI_NCR_MAX_TAGS)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1351) 	Max number of commands that can be queued to a host.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1352) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1353) SCSI_NCR_CMD_PER_LUN		(default: SCSI_NCR_MAX_TAGS)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1354) 	Max number of commands queued to a host for a device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1355) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1356) SCSI_NCR_SG_TABLESIZE		(default: SCSI_NCR_MAX_SCATTER-1)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1357) 	Max size of the Linux scatter/gather list.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1358) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1359) SCSI_NCR_MAX_LUN	(default: 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1360) 	Max number of LUNs per target.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1361) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1362) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1363) 12. Installation
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1364) ================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1365) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1366) This driver is part of the linux kernel distribution.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1367) Driver files are located in the sub-directory "drivers/scsi" of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1368) kernel source tree.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1369) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1370) Driver files::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1371) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1372) 	README.ncr53c8xx	: this file
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1373) 	ChangeLog.ncr53c8xx	: change log
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1374) 	ncr53c8xx.h		: definitions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1375) 	ncr53c8xx.c		: the driver code
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1376) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1377) New driver versions are made available separately in order to allow testing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1378) changes and new features prior to including them into the linux kernel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1379) distribution. The following URL provides information on latest available
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1380) patches:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1381) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1382)       ftp://ftp.tux.org/pub/people/gerard-roudier/README
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1383) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1384) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1385) 13. Architecture dependent features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1386) ===================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1387) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1388) <Not yet written>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1389) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1390) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1391) 14. Known problems
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1392) ==================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1393) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1394) 14.1 Tagged commands with Iomega Jaz device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1395) -------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1396) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1397) I have not tried this device, however it has been reported to me the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1398) following: This device is capable of Tagged command queuing. However
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1399) while spinning up, it rejects Tagged commands. This behaviour is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1400) conforms to 6.8.2 of SCSI-2 specifications. The current behaviour of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1401) the driver in that situation is not satisfying. So do not enable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1402) Tagged command queuing for devices that are able to spin down.  The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1403) other problem that may appear is timeouts. The only way to avoid
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1404) timeouts seems to edit linux/drivers/scsi/sd.c and to increase the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1405) current timeout values.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1406) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1407) 14.2 Device names change when another controller is added
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1408) ---------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1409) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1410) When you add a new NCR53C8XX chip based controller to a system that already
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1411) has one or more controllers of this family, it may happen that the order
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1412) the driver registers them to the kernel causes problems due to device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1413) name changes.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1414) When at least one controller uses NvRAM, SDMS BIOS version 4 allows you to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1415) define the order the BIOS will scan the scsi boards. The driver attaches
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1416) controllers according to BIOS information if NvRAM detect option is set.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1417) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1418) If your controllers do not have NvRAM, you can:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1419) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1420) - Ask the driver to probe chip ids in reverse order from the boot command
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1421)   line: ncr53c8xx=revprob:y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1422) - Make appropriate changes in the fstab.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1423) - Use the 'scsidev' tool from Eric Youngdale.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1424) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1425) 14.3 Using only 8 bit devices with a WIDE SCSI controller
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1426) ---------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1427) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1428) When only 8 bit NARROW devices are connected to a 16 bit WIDE SCSI controller,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1429) you must ensure that lines of the wide part of the SCSI BUS are pulled-up.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1430) This can be achieved by ENABLING the WIDE TERMINATOR portion of the SCSI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1431) controller card.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1432) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1433) The TYAN 1365 documentation revision 1.2 is not correct about such settings.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1434) (page 10, figure 3.3).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1435) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1436) 14.4 Possible data corruption during a Memory Write and Invalidate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1437) ------------------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1438) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1439) This problem is described in SYMBIOS DEL 397, Part Number 69-039241, ITEM 4.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1440) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1441) In some complex situations, 53C875 chips revision <= 3 may start a PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1442) Write and Invalidate Command at a not cache-line-aligned 4 DWORDS boundary.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1443) This is only possible when Cache Line Size is 8 DWORDS or greater.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1444) Pentium systems use a 8 DWORDS cache line size and so are concerned by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1445) this chip bug, unlike i486 systems that use a 4 DWORDS cache line size.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1446) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1447) When this situation occurs, the chip may complete the Write and Invalidate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1448) command after having only filled part of the last cache line involved in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1449) the transfer, leaving to data corruption the remainder of this cache line.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1450) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1451) Not using Write And Invalidate obviously gets rid of this chip bug, and so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1452) it is now the default setting of the driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1453) However, for people like me who want to enable this feature, I have added
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1454) part of a work-around suggested by SYMBIOS. This work-around resets the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1455) addressing logic when the DATA IN phase is entered and so prevents the bug
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1456) from being triggered for the first SCSI MOVE of the phase. This work-around
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1457) should be enough according to the following:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1458) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1459) The only driver internal data structure that is greater than 8 DWORDS  and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1460) that is moved by the SCRIPTS processor is the 'CCB header' that contains
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1461) the context of the SCSI transfer. This data structure is aligned on 8 DWORDS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1462) boundary (Pentium Cache Line Size), and so is immune to this chip bug, at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1463) least on Pentium systems.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1464) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1465) But the conditions of this bug can be met when a SCSI read command is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1466) performed using a buffer that is 4 DWORDS but not cache-line aligned.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1467) This cannot happen under Linux when scatter/gather lists are used since
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1468) they only refer to system buffers that are well aligned. So, a work around
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1469) may only be needed under Linux when a scatter/gather list is not used and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1470) when the SCSI DATA IN phase is reentered after a phase mismatch.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1471) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1472) 15. SCSI problem troubleshooting
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1473) ================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1474) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1475) 15.1 Problem tracking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1476) ---------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1477) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1478) Most SCSI problems are due to a non conformant SCSI bus or to buggy
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1479) devices.  If unfortunately you have SCSI problems, you can check the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1480) following things:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1481) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1482) - SCSI bus cables
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1483) - terminations at both end of the SCSI chain
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1484) - linux syslog messages (some of them may help you)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1485) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1486) If you do not find the source of problems, you can configure the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1487) driver with no features enabled.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1488) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1489) - only asynchronous data transfers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1490) - tagged commands disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1491) - disconnections not allowed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1492) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1493) Now, if your SCSI bus is ok, your system have every chance to work
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1494) with this safe configuration but performances will not be optimal.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1495) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1496) If it still fails, then you can send your problem description to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1497) appropriate mailing lists or news-groups.  Send me a copy in order to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1498) be sure I will receive it.  Obviously, a bug in the driver code is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1499) possible.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1500) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1501)      My email address: Gerard Roudier <groudier@free.fr>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1502) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1503) Allowing disconnections is important if you use several devices on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1504) your SCSI bus but often causes problems with buggy devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1505) Synchronous data transfers increases throughput of fast devices like
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1506) hard disks.  Good SCSI hard disks with a large cache gain advantage of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1507) tagged commands queuing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1508) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1509) Try to enable one feature at a time with control commands.  For example:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1510) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1511) ::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1512) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1513)     echo "setsync all 25" >/proc/scsi/ncr53c8xx/0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1514) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1515) Will enable fast synchronous data transfer negotiation for all targets.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1516) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1517) ::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1518) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1519)     echo "setflag 3" >/proc/scsi/ncr53c8xx/0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1520) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1521) Will reset flags (no_disc) for target 3, and so will allow it to disconnect
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1522) the SCSI Bus.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1523) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1524) ::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1525) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1526)     echo "settags 3 8" >/proc/scsi/ncr53c8xx/0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1527) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1528) Will enable tagged command queuing for target 3 if that device supports it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1529) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1530) Once you have found the device and the feature that cause problems, just
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1531) disable that feature for that device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1532) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1533) 15.2 Understanding hardware error reports
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1534) -----------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1535) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1536) When the driver detects an unexpected error condition, it may display a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1537) message of the following pattern::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1538) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1539)     sym53c876-0:1: ERROR (0:48) (1-21-65) (f/95) @ (script 7c0:19000000).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1540)     sym53c876-0: script cmd = 19000000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1541)     sym53c876-0: regdump: da 10 80 95 47 0f 01 07 75 01 81 21 80 01 09 00.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1542) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1543) Some fields in such a message may help you understand the cause of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1544) problem, as follows::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1545) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1546)     sym53c876-0:1: ERROR (0:48) (1-21-65) (f/95) @ (script 7c0:19000000).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1547)     ............A.........B.C....D.E..F....G.H.......I.....J...K.......
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1548) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1549) Field A : target number.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1550)   SCSI ID of the device the controller was talking with at the moment the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1551)   error occurs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1552) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1553) Field B : DSTAT io register (DMA STATUS)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1554)   ========   =============================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1555)   Bit 0x40   MDPE Master Data Parity Error
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1556)              Data parity error detected on the PCI BUS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1557)   Bit 0x20   BF   Bus Fault
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1558)              PCI bus fault condition detected
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1559)   Bit 0x01   IID  Illegal Instruction Detected
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1560)              Set by the chip when it detects an Illegal Instruction format
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1561)              on some condition that makes an instruction illegal.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1562)   Bit 0x80   DFE Dma Fifo Empty
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1563)              Pure status bit that does not indicate an error.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1564)   ========   =============================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1565) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1566)   If the reported DSTAT value contains a combination of MDPE (0x40),
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1567)   BF (0x20), then the cause may be likely due to a PCI BUS problem.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1568) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1569) Field C : SIST io register (SCSI Interrupt Status)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1570)   ========   ==================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1571)   Bit 0x08   SGE  SCSI GROSS ERROR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1572)              Indicates that the chip detected a severe error condition
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1573)              on the SCSI BUS that prevents the SCSI protocol from functioning
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1574)              properly.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1575)   Bit 0x04   UDC  Unexpected Disconnection
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1576)              Indicates that the device released the SCSI BUS when the chip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1577)              was not expecting this to happen. A device may behave so to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1578)              indicate the SCSI initiator that an error condition not reportable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1579)              using the SCSI protocol has occurred.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1580)   Bit 0x02   RST  SCSI BUS Reset
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1581)              Generally SCSI targets do not reset the SCSI BUS, although any
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1582)              device on the BUS can reset it at any time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1583)   Bit 0x01   PAR  Parity
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1584)              SCSI parity error detected.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1585)   ========   ==================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1586) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1587)   On a faulty SCSI BUS, any error condition among SGE (0x08), UDC (0x04) and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1588)   PAR (0x01) may be detected by the chip. If your SCSI system sometimes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1589)   encounters such error conditions, especially SCSI GROSS ERROR, then a SCSI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1590)   BUS problem is likely the cause of these errors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1591) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1592) For fields D,E,F,G and H, you may look into the sym53c8xx_defs.h file
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1593) that contains some minimal comments on IO register bits.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1594) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1595) Field D : SOCL  Scsi Output Control Latch
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1596)           This register reflects the state of the SCSI control lines the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1597)           chip want to drive or compare against.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1598) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1599) Field E : SBCL  Scsi Bus Control Lines
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1600)           Actual value of control lines on the SCSI BUS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1601) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1602) Field F : SBDL  Scsi Bus Data Lines
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1603)           Actual value of data lines on the SCSI BUS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1604) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1605) Field G : SXFER  SCSI Transfer
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1606)           Contains the setting of the Synchronous Period for output and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1607)           the current Synchronous offset (offset 0 means asynchronous).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1608) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1609) Field H : SCNTL3 Scsi Control Register 3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1610)           Contains the setting of timing values for both asynchronous and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1611)           synchronous data transfers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1612) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1613) Understanding Fields I, J, K and dumps requires to have good knowledge of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1614) SCSI standards, chip cores functionnals and internal driver data structures.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1615) You are not required to decode and understand them, unless you want to help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1616) maintain the driver code.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1617) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1618) 16. Synchronous transfer negotiation tables
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1619) ===========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1620) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1621) Tables below have been created by calling the routine the driver uses
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1622) for synchronisation negotiation timing calculation and chip setting.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1623) The first table corresponds to Ultra chips 53875 and 53C860 with 80 MHz
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1624) clock and 5 clock divisors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1625) The second one has been calculated by setting the scsi clock to 40 Mhz
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1626) and using 4 clock divisors and so applies to all NCR53C8XX chips in fast
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1627) SCSI-2 mode.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1628) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1629) Periods are in nano-seconds and speeds are in Mega-transfers per second.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1630) 1 Mega-transfers/second means 1 MB/s with 8 bits SCSI and 2 MB/s with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1631) Wide16 SCSI.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1632) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1633) 16.1 Synchronous timings for 53C895, 53C875 and 53C860 SCSI controllers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1634) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1635) +-----------------------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1636) |Negotiated                   |NCR settings    |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1637) +-------+--------+------------+--------+-------+              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1638) |Factor |Period  |Speed       |Period  |Speed  |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1639) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1640) |10     | 25     |40.000      | 25     |40.000 | (53C895 only)|
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1641) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1642) |11     | 30.2   |33.112      | 31.25  |32.000 | (53C895 only)|
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1643) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1644) |12     | 50     |20.000      | 50     |20.000 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1645) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1646) |13     | 52     |19.230      | 62     |16.000 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1647) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1648) |14     | 56     |17.857      | 62     |16.000 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1649) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1650) |15     | 60     |16.666      | 62     |16.000 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1651) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1652) |16     | 64     |15.625      | 75     |13.333 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1653) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1654) |17     | 68     |14.705      | 75     |13.333 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1655) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1656) |18     | 72     |13.888      | 75     |13.333 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1657) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1658) |19     | 76     |13.157      | 87     |11.428 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1659) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1660) |20     | 80     |12.500      | 87     |11.428 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1661) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1662) |21     | 84     |11.904      | 87     |11.428 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1663) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1664) |22     | 88     |11.363      | 93     |10.666 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1665) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1666) |23     | 92     |10.869      | 93     |10.666 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1667) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1668) |24     | 96     |10.416      |100     |10.000 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1669) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1670) |25     |100     |10.000      |100     |10.000 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1671) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1672) |26     |104     | 9.615      |112     | 8.888 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1673) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1674) |27     |108     | 9.259      |112     | 8.888 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1675) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1676) |28     |112     | 8.928      |112     | 8.888 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1677) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1678) |29     |116     | 8.620      |125     | 8.000 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1679) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1680) |30     |120     | 8.333      |125     | 8.000 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1681) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1682) |31     |124     | 8.064      |125     | 8.000 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1683) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1684) |32     |128     | 7.812      |131     | 7.619 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1685) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1686) |33     |132     | 7.575      |150     | 6.666 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1687) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1688) |34     |136     | 7.352      |150     | 6.666 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1689) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1690) |35     |140     | 7.142      |150     | 6.666 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1691) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1692) |36     |144     | 6.944      |150     | 6.666 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1693) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1694) |37     |148     | 6.756      |150     | 6.666 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1695) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1696) |38     |152     | 6.578      |175     | 5.714 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1697) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1698) |39     |156     | 6.410      |175     | 5.714 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1699) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1700) |40     |160     | 6.250      |175     | 5.714 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1701) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1702) |41     |164     | 6.097      |175     | 5.714 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1703) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1704) |42     |168     | 5.952      |175     | 5.714 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1705) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1706) |43     |172     | 5.813      |175     | 5.714 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1707) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1708) |44     |176     | 5.681      |187     | 5.333 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1709) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1710) |45     |180     | 5.555      |187     | 5.333 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1711) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1712) |46     |184     | 5.434      |187     | 5.333 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1713) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1714) |47     |188     | 5.319      |200     | 5.000 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1715) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1716) |48     |192     | 5.208      |200     | 5.000 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1717) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1718) |49     |196     | 5.102      |200     | 5.000 |              |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1719) +-------+--------+------------+--------+-------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1720) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1721) 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1722) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1723) +-----------------------------+----------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1724) |Negotiated                   |NCR settings    |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1725) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1726) |Factor |Period  |Speed       |Period  |Speed  |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1727) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1728) |25     |100     |10.000      |100     |10.000 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1729) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1730) |26     |104     |9.615       |125     | 8.000 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1731) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1732) |27     |108     |9.259       |125     | 8.000 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1733) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1734) |28     |112     |8.928       |125     | 8.000 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1735) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1736) |29     |116     |8.620       |125     | 8.000 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1737) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1738) |30     |120     |8.333       |125     | 8.000 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1739) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1740) |31     |124     |8.064       |125     | 8.000 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1741) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1742) |32     |128     |7.812       |131     | 7.619 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1743) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1744) |33     |132     |7.575       |150     | 6.666 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1745) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1746) |34     |136     |7.352       |150     | 6.666 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1747) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1748) |35     |140     |7.142       |150     | 6.666 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1749) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1750) |36     |144     |6.944       |150     | 6.666 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1751) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1752) |37     |148     |6.756       |150     | 6.666 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1753) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1754) |38     |152     |6.578       |175     | 5.714 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1755) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1756) |39     |156     |6.410       |175     | 5.714 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1757) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1758) |40     |160     |6.250       |175     | 5.714 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1759) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1760) |41     |164     |6.097       |175     | 5.714 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1761) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1762) |42     |168     |5.952       |175     | 5.714 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1763) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1764) |43     |172     |5.813       |175     | 5.714 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1765) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1766) |44     |176     |5.681       |187     | 5.333 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1767) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1768) |45     |180     |5.555       |187     | 5.333 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1769) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1770) |46     |184     |5.434       |187     | 5.333 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1771) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1772) |47     |188     |5.319       |200     | 5.000 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1773) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1774) |48     |192     |5.208       |200     | 5.000 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1775) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1776) |49     |196     |5.102       |200     | 5.000 |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1777) +-------+--------+------------+--------+-------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1778) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1779) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1780) 17. Serial NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1781) ================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1782) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1783) (added by Richard Waltham: dormouse@farsrobt.demon.co.uk)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1784) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1785) 17.1 Features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1786) -------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1787) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1788) Enabling serial NVRAM support enables detection of the serial NVRAM included
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1789) on Symbios and some Symbios compatible host adaptors, and Tekram boards. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1790) serial NVRAM is used by Symbios and Tekram to hold set up parameters for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1791) host adaptor and its attached drives.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1792) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1793) The Symbios NVRAM also holds data on the boot order of host adaptors in a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1794) system with more than one host adaptor. This enables the order of scanning
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1795) the cards for drives to be changed from the default used during host adaptor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1796) detection.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1797) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1798) This can be done to a limited extent at the moment using "reverse probe" but
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1799) this only changes the order of detection of different types of cards. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1800) NVRAM boot order settings can do this as well as change the order the same
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1801) types of cards are scanned in, something "reverse probe" cannot do.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1802) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1803) Tekram boards using Symbios chips, DC390W/F/U, which have NVRAM are detected
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1804) and this is used to distinguish between Symbios compatible and Tekram host
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1805) adaptors. This is used to disable the Symbios compatible "diff" setting
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1806) incorrectly set on Tekram boards if the CONFIG_SCSI_53C8XX_SYMBIOS_COMPAT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1807) configuration parameter is set enabling both Symbios and Tekram boards to be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1808) used together with the Symbios cards using all their features, including
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1809) "diff" support. ("led pin" support for Symbios compatible cards can remain
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1810) enabled when using Tekram cards. It does nothing useful for Tekram host
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1811) adaptors but does not cause problems either.)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1812) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1813) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1814) 17.2 Symbios NVRAM layout
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1815) -------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1816) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1817) typical data at NVRAM address 0x100 (53c810a NVRAM)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1818) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1819)     00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1820)     64 01
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1821)     8e 0b
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1822) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1823)     00 30 00 00 00 00 07 00 00 00 00 00 00 00 07 04 10 04 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1824) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1825)     04 00 0f 00 00 10 00 50 00 00 01 00 00 62
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1826)     04 00 03 00 00 10 00 58 00 00 01 00 00 63
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1827)     04 00 01 00 00 10 00 48 00 00 01 00 00 61
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1828)     00 00 00 00 00 00 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1829) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1830)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1831)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1832)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1833)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1834)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1835)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1836)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1837)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1838) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1839)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1840)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1841)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1842)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1843)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1844)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1845)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1846)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1847) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1848)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1849)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1850)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1851)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1852)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1853)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1854)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1855)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1856) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1857)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1858)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1859)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1860)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1861)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1862)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1863)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1864)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1865) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1866)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1867)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1868)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1869) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1870)     fe fe
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1871)     00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1872)     00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1873) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1874) NVRAM layout details
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1875) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1876) =============  ================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1877) NVRAM Address
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1878) =============  ================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1879) 0x000-0x0ff    not used
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1880) 0x100-0x26f    initialised data
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1881) 0x270-0x7ff    not used
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1882) =============  ================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1883) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1884) general layout::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1885) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1886)         header  -   6 bytes,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1887)         data    - 356 bytes (checksum is byte sum of this data)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1888)         trailer -   6 bytes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1889)                   ---
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1890)         total     368 bytes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1891) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1892) data area layout::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1893) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1894)         controller set up  -  20 bytes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1895)         boot configuration -  56 bytes (4x14 bytes)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1896)         device set up      - 128 bytes (16x8 bytes)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1897)         unused (spare?)    - 152 bytes (19x8 bytes)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1898)                              ---
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1899)         total                356 bytes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1900) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1901) header::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1902) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1903)     00 00   - ?? start marker
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1904)     64 01   - byte count (lsb/msb excludes header/trailer)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1905)     8e 0b   - checksum (lsb/msb excludes header/trailer)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1906) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1907) controller set up::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1908) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1909)     00 30 00 00 00 00 07 00 00 00 00 00 00 00 07 04 10 04 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1910) 		    |     |           |     |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1911) 		    |     |           |      -- host ID
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1912) 		    |     |           |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1913) 		    |     |            --Removable Media Support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1914) 		    |     |               0x00 = none
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1915) 		    |     |               0x01 = Bootable Device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1916) 		    |     |               0x02 = All with Media
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1917) 		    |     |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1918) 		    |      --flag bits 2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1919) 		    |        0x00000001= scan order hi->low
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1920) 		    |            (default 0x00 - scan low->hi)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1921) 			--flag bits 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1922) 			0x00000001 scam enable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1923) 			0x00000010 parity enable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1924) 			0x00000100 verbose boot msgs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1925) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1926) remaining bytes unknown - they do not appear to change in my
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1927) current set up for any of the controllers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1928) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1929) default set up is identical for 53c810a and 53c875 NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1930) (Removable Media added Symbios BIOS version 4.09)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1931) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1932) boot configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1933) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1934) boot order set by order of the devices in this table::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1935) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1936)     04 00 0f 00 00 10 00 50 00 00 01 00 00 62 -- 1st controller
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1937)     04 00 03 00 00 10 00 58 00 00 01 00 00 63    2nd controller
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1938)     04 00 01 00 00 10 00 48 00 00 01 00 00 61    3rd controller
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1939)     00 00 00 00 00 00 00 00 00 00 00 00 00 00    4th controller
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1940) 	|  |  |  |     |        |     |  |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1941) 	|  |  |  |     |        |      ---- PCI io port adr
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1942) 	|  |  |  |     |         --0x01 init/scan at boot time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1943) 	|  |  |  |      --PCI device/function number (0xdddddfff)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1944) 	|  |   ----- ?? PCI vendor ID (lsb/msb)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1945) 	    ----PCI device ID (lsb/msb)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1946) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1947)     ?? use of this data is a guess but seems reasonable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1948) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1949) remaining bytes unknown - they do not appear to change in my
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1950) current set up
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1951) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1952) default set up is identical for 53c810a and 53c875 NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1953) --------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1954) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1955) device set up (up to 16 devices - includes controller)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1956) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1957)     0f 00 08 08 64 00 0a 00 - id 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1958)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1959)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1960)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1961)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1962)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1963)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1964)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1965) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1966)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1967)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1968)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1969)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1970)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1971)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1972)     0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1973)     0f 00 08 08 64 00 0a 00 - id 15
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1974)     |     |  |  |     |  |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1975)     |     |  |  |      ----timeout (lsb/msb)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1976)     |     |  |   --synch period (0x?? 40 Mtrans/sec- fast 40) (probably 0x28)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1977)     |     |  |                  (0x30 20 Mtrans/sec- fast 20)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1978)     |     |  |                  (0x64 10 Mtrans/sec- fast )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1979)     |     |  |                  (0xc8  5 Mtrans/sec)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1980)     |     |  |                  (0x00  asynchronous)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1981)     |     |   -- ?? max sync offset (0x08 in NVRAM on 53c810a)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1982)     |     |                         (0x10 in NVRAM on 53c875)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1983)     |      --device bus width (0x08 narrow)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1984)     |                         (0x10 16 bit wide)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1985)     --flag bits
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1986) 	0x00000001 - disconnect enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1987) 	0x00000010 - scan at boot time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1988) 	0x00000100 - scan luns
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1989) 	0x00001000 - queue tags enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1990) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1991) remaining bytes unknown - they do not appear to change in my
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1992) current set up
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1993) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1994) ?? use of this data is a guess but seems reasonable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1995) (but it could be max bus width)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1996) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1997) default set up for 53c810a NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1998) default set up for 53c875 NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1999) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2000) 				- bus width     - 0x10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2001)                                 - sync offset ? - 0x10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2002)                                 - sync period   - 0x30
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2003) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2004) ?? spare device space (32 bit bus ??)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2005) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2006) ::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2007) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2008)     00 00 00 00 00 00 00 00  (19x8bytes)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2009)     .
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2010)     .
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2011)     00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2012) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2013) default set up is identical for 53c810a and 53c875 NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2014) --------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2015) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2016) trailer::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2017) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2018)     fe fe   - ? end marker ?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2019)     00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2020)     00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2021) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2022) default set up is identical for 53c810a and 53c875 NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2023) -----------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2024) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2025) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2026) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2027) 17.3 Tekram NVRAM layout
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2028) ------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2029) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2030) nvram 64x16 (1024 bit)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2031) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2032) Drive settings::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2033) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2034)     Drive ID 0-15 (addr 0x0yyyy0 = device setup, yyyy = ID)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2035) 		(addr 0x0yyyy1 = 0x0000)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2036) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2037) 	x x x x  x x x x  x x x x  x x x x
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2038) 		| | |      | |  | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2039) 		| | |      | |  | | |  ----- parity check   0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2040) 		| | |      | |  | | |                       1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2041) 		| | |      | |  | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2042) 		| | |      | |  | |  ------- sync neg       0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2043) 		| | |      | |  | |                         1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2044) 		| | |      | |  | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2045) 		| | |      | |  |  --------- disconnect     0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2046) 		| | |      | |  |                           1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2047) 		| | |      | |  |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2048) 		| | |      | |   ----------- start cmd      0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2049) 		| | |      | |                              1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2050) 		| | |      | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2051) 		| | |      |  -------------- tagged cmds    0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2052) 		| | |      |                                1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2053) 		| | |      |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2054) 		| | |       ---------------- wide neg       0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2055) 		| | |                                       1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2056) 		| | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2057) 		    --------------------------- sync rate      0 - 10.0 Mtrans/sec
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2058) 							    1 -  8.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2059) 							    2 -  6.6
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2060) 							    3 -  5.7
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2061) 							    4 -  5.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2062) 							    5 -  4.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2063) 							    6 -  3.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2064) 							    7 -  2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2065) 							    7 -  2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2066) 							    8 - 20.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2067) 							    9 - 16.7
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2068) 							    a - 13.9
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2069) 							    b - 11.9
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2070) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2071) Global settings
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2072) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2073) Host flags 0 (addr 0x100000, 32)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2074) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2075)     x x x x  x x x x  x x x x  x x x x
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2076)     | | | |  | | | |           | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2077)     | | | |  | | | |            ----------- host ID    0x00 - 0x0f
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2078)     | | | |  | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2079)     | | | |  | | |  ----------------------- support for    0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2080)     | | | |  | | |                          > 2 drives     1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2081)     | | | |  | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2082)     | | | |  | |  ------------------------- support drives 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2083)     | | | |  | |                            > 1Gbytes      1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2084)     | | | |  | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2085)     | | | |  |  --------------------------- bus reset on   0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2086)     | | | |  |                                power on     1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2087)     | | | |  |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2088)     | | | |   ----------------------------- active neg     0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2089)     | | | |                                                1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2090)     | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2091)     | | |  -------------------------------- imm seek       0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2092)     | | |                                                  1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2093)     | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2094)     | |  ---------------------------------- scan luns      0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2095)     | |                                                    1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2096)     | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2097)      -------------------------------------- removable      0 - disable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2098)                                             as BIOS dev    1 - boot device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2099)                                                            2 - all
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2100) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2101) Host flags 1 (addr 0x100001, 33)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2102) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2103)     x x x x  x x x x  x x x x  x x x x
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2104)                | | |             | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2105)                | | |              --------- boot delay     0 -   3 sec
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2106)                | | |                                       1 -   5
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2107)                | | |                                       2 -  10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2108)                | | |                                       3 -  20
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2109)                | | |                                       4 -  30
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2110)                | | |                                       5 -  60
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2111)                | | |                                       6 - 120
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2112)                | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2113)                 --------------------------- max tag cmds   0 -  2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2114)                                                            1 -  4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2115)                                                            2 -  8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2116)                                                            3 - 16
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2117)                                                            4 - 32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2118) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2119) Host flags 2 (addr 0x100010, 34)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2120) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2121)     x x x x  x x x x  x x x x  x x x x
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2122)                                      |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2123)                                       ----- F2/F6 enable   0 - off ???
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2124)                                                            1 - on  ???
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2125) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2126) checksum (addr 0x111111)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2127) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2128) checksum = 0x1234 - (sum addr 0-63)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2129) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2130) ----------------------------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2131) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2132) default nvram data::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2133) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2134)     0x0037 0x0000 0x0037 0x0000 0x0037 0x0000 0x0037 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2135)     0x0037 0x0000 0x0037 0x0000 0x0037 0x0000 0x0037 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2136)     0x0037 0x0000 0x0037 0x0000 0x0037 0x0000 0x0037 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2137)     0x0037 0x0000 0x0037 0x0000 0x0037 0x0000 0x0037 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2138) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2139)     0x0f07 0x0400 0x0001 0x0000 0x0000 0x0000 0x0000 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2140)     0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2141)     0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2142)     0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0xfbbc
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2143) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2144) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2145) 18. Support for Big Endian
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2146) ==========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2147) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2148) The PCI local bus has been primarily designed for x86 architecture.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2149) As a consequence, PCI devices generally expect DWORDS using little endian
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2150) byte ordering.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2151) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2152) 18.1 Big Endian CPU
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2153) -------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2154) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2155) In order to support NCR chips on a Big Endian architecture the driver has to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2156) perform byte reordering each time it is needed. This feature has been
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2157) added to the driver by Cort <cort@cs.nmt.edu> and is available in driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2158) version 2.5 and later ones. For the moment Big Endian support has only
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2159) been tested on Linux/PPC (PowerPC).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2160) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2161) 18.2 NCR chip in Big Endian mode of operations
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2162) ----------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2163) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2164) It can be read in SYMBIOS documentation that some chips support a special
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2165) Big Endian mode, on paper: 53C815, 53C825A, 53C875, 53C875N, 53C895.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2166) This mode of operations is not software-selectable, but needs pin named
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2167) BigLit to be pulled-up. Using this mode, most of byte reorderings should
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2168) be avoided when the driver is running on a Big Endian CPU.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2169) Driver version 2.5 is also, in theory, ready for this feature.