^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 SYM-2 driver documentation 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) Updated by Matthew Wilcox <matthew@wil.cx>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) 2004-10-09
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) .. Contents
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) 1. Introduction
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) 2. Supported chips and SCSI features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) 3. Advantages of this driver for newer chips.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) 3.1 Optimized SCSI SCRIPTS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) 3.2 New features appeared with the SYM53C896
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) 4. Memory mapped I/O versus normal I/O
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) 5. Tagged command queueing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) 6. Parity checking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) 7. Profiling information
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) 8. Control commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) 8.1 Set minimum synchronous period
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) 8.2 Set wide size
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) 8.3 Set maximum number of concurrent tagged commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) 8.4 Set debug mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) 8.5 Set flag (no_disc)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) 8.6 Set verbose level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) 8.7 Reset all logical units of a target
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) 8.8 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 Default number of tagged commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) 10.2.2 Burst max
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) 10.2.3 LED support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) 10.2.4 Differential mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) 10.2.5 IRQ mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) 10.2.6 Check SCSI BUS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) 10.2.7 Suggest a default SCSI id for hosts
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) 10.2.8 Verbosity level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) 10.2.9 Debug mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) 10.2.10 Settle delay
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) 10.2.11 Serial NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) 10.2.12 Exclude a host from being attached
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) 10.3 Converting from old options
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) 10.4 SCSI BUS checking boot option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) 11. SCSI problem troubleshooting
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) 15.1 Problem tracking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) 15.2 Understanding hardware error reports
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) 12. Serial NVRAM support (by Richard Waltham)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) 17.1 Features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) 17.2 Symbios NVRAM layout
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) 17.3 Tekram NVRAM layout
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) 1. Introduction
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) ===============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) This driver supports the whole SYM53C8XX family of PCI-SCSI controllers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) It also support the subset of LSI53C10XX PCI-SCSI controllers that are based
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) on the SYM53C8XX SCRIPTS language.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) It replaces the sym53c8xx+ncr53c8xx driver bundle and shares its core code
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) with the FreeBSD SYM-2 driver. The 'glue' that allows this driver to work
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) under Linux is contained in 2 files named sym_glue.h and sym_glue.c.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) Other drivers files are intended not to depend on the Operating System
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) on which the driver is used.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77) The history of this driver can be summarized as follows:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) 1993: ncr driver written for 386bsd and FreeBSD by:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) - Wolfgang Stanglmeier <wolf@cologne.de>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) - Stefan Esser <se@mi.Uni-Koeln.de>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) 1996: port of the ncr driver to Linux-1.2.13 and rename it ncr53c8xx.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) - Gerard Roudier
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) 1998: new sym53c8xx driver for Linux based on LOAD/STORE instruction and that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) adds full support for the 896 but drops support for early NCR devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) - Gerard Roudier
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) 1999: port of the sym53c8xx driver to FreeBSD and support for the LSI53C1010
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94) 33 MHz and 66MHz Ultra-3 controllers. The new driver is named 'sym'.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96) - Gerard Roudier
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) 2000: Add support for early NCR devices to FreeBSD 'sym' driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) Break the driver into several sources and separate the OS glue
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) code from the core code that can be shared among different O/Ses.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) Write a glue code for Linux.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) - Gerard Roudier
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) 2004: Remove FreeBSD compatibility code. Remove support for versions of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) Linux before 2.6. Start using Linux facilities.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) This README file addresses the Linux version of the driver. Under FreeBSD,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) the driver documentation is the sym.8 man page.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) Information about new chips is available at LSILOGIC web server:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) http://www.lsilogic.com/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) SCSI standard documentations are available at T10 site:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) http://www.t10.org/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) Useful SCSI tools written by Eric Youngdale are part of most Linux
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) distributions:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) ============ ==========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) scsiinfo command line tool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) scsi-config TCL/Tk tool using scsiinfo
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) ============ ==========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) 2. Supported chips and SCSI features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) ====================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) The following features are supported for all chips:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) - Synchronous negotiation
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) - Disconnection
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) - Tagged command queuing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) - SCSI parity checking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) - PCI Master parity checking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) Other features depends on chip capabilities.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) The driver notably uses optimized SCRIPTS for devices that support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) LOAD/STORE and handles PHASE MISMATCH from SCRIPTS for devices that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) support the corresponding feature.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) The following table shows some characteristics of the chip family.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) | | | | | |Load/store |Hardware |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) | |On board | | | |scripts |phase |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) |Chip |SDMS BIOS |Wide |SCSI std. | Max. sync | |mismatch |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) |810 | N | N | FAST10 | 10 MB/s | N | N |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) |810A | N | N | FAST10 | 10 MB/s | Y | N |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) |815 | Y | N | FAST10 | 10 MB/s | N | N |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) |825 | Y | Y | FAST10 | 20 MB/s | N | N |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) |825A | Y | Y | FAST10 | 20 MB/s | Y | N |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) |860 | N | N | FAST20 | 20 MB/s | Y | N |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) |875 | Y | Y | FAST20 | 40 MB/s | Y | N |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) |875A | Y | Y | FAST20 | 40 MB/s | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) |876 | Y | Y | FAST20 | 40 MB/s | Y | N |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) |895 | Y | Y | FAST40 | 80 MB/s | Y | N |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) |895A | Y | Y | FAST40 | 80 MB/s | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) |896 | Y | Y | FAST40 | 80 MB/s | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175) |897 | Y | Y | FAST40 | 80 MB/s | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) |1510D | Y | Y | FAST40 | 80 MB/s | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) |1010 | Y | Y | FAST80 |160 MB/s | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) |1010_66 | Y | Y | FAST80 |160 MB/s | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) |[1]_ | | | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) +--------+-----------+-----+-----------+------------+------------+---------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) .. [1] Chip supports 33MHz and 66MHz PCI bus clock.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) Summary of other supported features:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) :Module: allow to load the driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) :Memory mapped I/O: increases performance
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) :Control commands: write operations to the proc SCSI file system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) :Debugging information: written to syslog (expert only)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) :Serial NVRAM: Symbios and Tekram formats
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) - Scatter / gather
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) - Shared interrupt
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) - Boot setup commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) 3. Advantages of this driver for newer chips.
^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) 3.1 Optimized SCSI SCRIPTS
^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) All chips except the 810, 815 and 825, support new SCSI SCRIPTS instructions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) 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 209) to/from memory much faster that the MOVE MEMORY instruction that is supported
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) by the 53c7xx and 53c8xx family.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) The LOAD/STORE instructions support absolute and DSA relative addressing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) modes. The SCSI SCRIPTS had been entirely rewritten using LOAD/STORE instead
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) of MOVE MEMORY instructions.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) Due to the lack of LOAD/STORE SCRIPTS instructions by earlier chips, this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) driver also incorporates a different SCRIPTS set based on MEMORY MOVE, in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) order to provide support for the entire SYM53C8XX chips family.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) 3.2 New features appeared with the SYM53C896
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) --------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) Newer chips (see above) allows handling of the phase mismatch context from
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) SCRIPTS (avoids the phase mismatch interrupt that stops the SCSI processor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) until the C code has saved the context of the transfer).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227) The 896 and 1010 chips support 64 bit PCI transactions and addressing,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228) while the 895A supports 32 bit PCI transactions and 64 bit addressing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) The SCRIPTS processor of these chips is not true 64 bit, but uses segment
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) registers for bit 32-63. Another interesting feature is that LOAD/STORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) instructions that address the on-chip RAM (8k) remain internal to the chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233) 4. Memory mapped I/O versus normal I/O
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234) ======================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) Memory mapped I/O has less latency than normal I/O and is the recommended
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) way for doing IO with PCI devices. Memory mapped I/O seems to work fine on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) most hardware configurations, but some poorly designed chipsets may break
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) this feature. A configuration option is provided for normal I/O to be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) used but the driver defaults to MMIO.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242) 5. Tagged command queueing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243) ==========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) Queuing more than 1 command at a time to a device allows it to perform
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246) optimizations based on actual head positions and its mechanical
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) characteristics. This feature may also reduce average command latency.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248) In order to really gain advantage of this feature, devices must have
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) a reasonable cache size (No miracle is to be expected for a low-end
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) hard disk with 128 KB or less).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252) Some known old SCSI devices do not properly support tagged command queuing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253) Generally, firmware revisions that fix this kind of problems are available
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254) at respective vendor web/ftp sites.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256) All I can say is that I never have had problem with tagged queuing using
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257) this driver and its predecessors. Hard disks that behaved correctly for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258) me using tagged commands are the following:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260) - IBM S12 0662
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261) - Conner 1080S
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262) - Quantum Atlas I
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263) - Quantum Atlas II
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) - Seagate Cheetah I
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265) - Quantum Viking II
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) - IBM DRVS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267) - Quantum Atlas IV
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268) - Seagate Cheetah II
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270) If your controller has NVRAM, you can configure this feature per target
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271) from the user setup tool. The Tekram Setup program allows to tune the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 272) maximum number of queued commands up to 32. The Symbios Setup only allows
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 273) to enable or disable this feature.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 274)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 275) The maximum number of simultaneous tagged commands queued to a device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 276) is currently set to 16 by default. This value is suitable for most SCSI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 277) disks. With large SCSI disks (>= 2GB, cache >= 512KB, average seek time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 278) <= 10 ms), using a larger value may give better performances.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 279)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 280) This driver supports up to 255 commands per device, and but using more than
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 281) 64 is generally not worth-while, unless you are using a very large disk or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 282) disk arrays. It is noticeable that most of recent hard disks seem not to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 283) accept more than 64 simultaneous commands. So, using more than 64 queued
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 284) commands is probably just resource wasting.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 285)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 286) If your controller does not have NVRAM or if it is managed by the SDMS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 287) BIOS/SETUP, you can configure tagged queueing feature and device queue
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 288) depths from the boot command-line. For example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 289)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 290) sym53c8xx=tags:4/t2t3q15-t4q7/t1u0q32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 291)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 292) will set tagged commands queue depths as follow:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 293)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 294) - target 2 all luns on controller 0 --> 15
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 295) - target 3 all luns on controller 0 --> 15
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 296) - target 4 all luns on controller 0 --> 7
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 297) - target 1 lun 0 on controller 1 --> 32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 298) - all other target/lun --> 4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 299)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 300) In some special conditions, some SCSI disk firmwares may return a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 301) QUEUE FULL status for a SCSI command. This behaviour is managed by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 302) driver using the following heuristic:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 303)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 304) - Each time a QUEUE FULL status is returned, tagged queue depth is reduced
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 305) to the actual number of disconnected commands.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 306)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 307) - Every 200 successfully completed SCSI commands, if allowed by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 308) current limit, the maximum number of queueable commands is incremented.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 309)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 310) Since QUEUE FULL status reception and handling is resource wasting, the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 311) driver notifies by default this problem to user by indicating the actual
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 312) number of commands used and their status, as well as its decision on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 313) device queue depth change.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 314) The heuristic used by the driver in handling QUEUE FULL ensures that the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 315) impact on performances is not too bad. You can get rid of the messages by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 316) setting verbose level to zero, as follow:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 317)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 318) 1st method:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 319) boot your system using 'sym53c8xx=verb:0' option.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 320) 2nd method:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 321) apply "setverbose 0" control command to the proc fs entry
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 322) corresponding to your controller after boot-up.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 323)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 324) 6. Parity checking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 325) ==================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 326)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 327) The driver supports SCSI parity checking and PCI bus master parity
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 328) checking. These features must be enabled in order to ensure safe
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 329) data transfers. Some flawed devices or mother boards may have problems
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 330) with parity. The options to defeat parity checking have been removed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 331) from the driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 332)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 333) 7. Profiling information
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 334) ========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 335)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 336) This driver does not provide profiling information as did its predecessors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 337) This feature was not this useful and added complexity to the code.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 338) As the driver code got more complex, I have decided to remove everything
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 339) that didn't seem actually useful.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 340)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 341) 8. Control commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 342) ===================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 343)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 344) Control commands can be sent to the driver with write operations to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 345) the proc SCSI file system. The generic command syntax is the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 346) following::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 347)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 348) echo "<verb> <parameters>" >/proc/scsi/sym53c8xx/0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 349) (assumes controller number is 0)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 350)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 351) Using "all" for "<target>" parameter with the commands below will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 352) apply to all targets of the SCSI chain (except the controller).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 353)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 354) Available commands:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 355)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 356) 8.1 Set minimum synchronous period factor
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 357) -----------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 358)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 359) setsync <target> <period factor>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 360)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 361) :target: target number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 362) :period: minimum synchronous period.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 363) Maximum speed = 1000/(4*period factor) except for special
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 364) cases below.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 365)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 366) Specify a period of 0, to force asynchronous transfer mode.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 367)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 368) - 9 means 12.5 nano-seconds synchronous period
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 369) - 10 means 25 nano-seconds synchronous period
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 370) - 11 means 30 nano-seconds synchronous period
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 371) - 12 means 50 nano-seconds synchronous period
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 372)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 373) 8.2 Set wide size
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 374) -----------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 375)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 376) setwide <target> <size>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 377)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 378) :target: target number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 379) :size: 0=8 bits, 1=16bits
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 380)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 381) 8.3 Set maximum number of concurrent tagged commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 382) ----------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 383)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 384) settags <target> <tags>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 385)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 386) :target: target number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 387) :tags: number of concurrent tagged commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 388) must not be greater than configured (default: 16)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 389)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 390) 8.4 Set debug mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 391) ------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 392)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 393) setdebug <list of debug flags>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 394)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 395) Available debug flags:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 396)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 397) ======== ========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 398) alloc print info about memory allocations (ccb, lcb)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 399) queue print info about insertions into the command start queue
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 400) result print sense data on CHECK CONDITION status
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 401) scatter print info about the scatter process
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 402) scripts print info about the script binding process
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 403) tiny print minimal debugging information
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 404) timing print timing information of the NCR chip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 405) nego print information about SCSI negotiations
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 406) phase print information on script interruptions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 407) ======== ========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 408)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 409) Use "setdebug" with no argument to reset debug flags.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 410)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 411)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 412) 8.5 Set flag (no_disc)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 413) ----------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 414)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 415) setflag <target> <flag>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 416)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 417) :target: target number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 418)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 419) For the moment, only one flag is available:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 420)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 421) no_disc: not allow target to disconnect.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 422)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 423) Do not specify any flag in order to reset the flag. For example:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 424)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 425) setflag 4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 426) will reset no_disc flag for target 4, so will allow it disconnections.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 427) setflag all
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 428) will allow disconnection for all devices on the SCSI bus.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 429)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 430)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 431) 8.6 Set verbose level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 432) ---------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 433)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 434) setverbose #level
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 435)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 436) The driver default verbose level is 1. This command allows to change
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 437) th driver verbose level after boot-up.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 438)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 439) 8.7 Reset all logical units of a target
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 440) ---------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 441)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 442) resetdev <target>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 443)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 444) :target: target number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 445)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 446) The driver will try to send a BUS DEVICE RESET message to the target.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 447)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 448) 8.8 Abort all tasks of all logical units of a target
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 449) ----------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 450)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 451) cleardev <target>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 452)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 453) :target: target number
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 454)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 455) The driver will try to send a ABORT message to all the logical units
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 456) of the target.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 457)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 458)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 459) 9. Configuration parameters
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 460) ===========================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 461)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 462) Under kernel configuration tools (make menuconfig, for example), it is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 463) possible to change some default driver configuration parameters.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 464) If the firmware of all your devices is perfect enough, all the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 465) features supported by the driver can be enabled at start-up. However,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 466) if only one has a flaw for some SCSI feature, you can disable the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 467) support by the driver of this feature at linux start-up and enable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 468) this feature after boot-up only for devices that support it safely.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 469)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 470) Configuration parameters:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 471)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 472) Use normal IO (default answer: n)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 473) Answer "y" if you suspect your mother board to not allow memory mapped I/O.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 474) May slow down performance a little.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 475)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 476) Default tagged command queue depth (default answer: 16)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 477) Entering 0 defaults to tagged commands not being used.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 478) This parameter can be specified from the boot command line.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 479)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 480) Maximum number of queued commands (default answer: 32)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 481) This option allows you to specify the maximum number of tagged commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 482) that can be queued to a device. The maximum supported value is 255.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 483)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 484) Synchronous transfers frequency (default answer: 80)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 485) This option allows you to specify the frequency in MHz the driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 486) will use at boot time for synchronous data transfer negotiations.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 487) 0 means "asynchronous data transfers".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 488)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 489) 10. Boot setup commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 490) =======================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 491)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 492) 10.1 Syntax
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 493) -----------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 494)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 495) Setup commands can be passed to the driver either at boot time or as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 496) parameters to modprobe, as described in Documentation/admin-guide/kernel-parameters.rst
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 497)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 498) Example of boot setup command under lilo prompt::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 499)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 500) lilo: linux root=/dev/sda2 sym53c8xx.cmd_per_lun=4 sym53c8xx.sync=10 sym53c8xx.debug=0x200
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 501)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 502) - enable tagged commands, up to 4 tagged commands queued.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 503) - set synchronous negotiation speed to 10 Mega-transfers / second.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 504) - set DEBUG_NEGO flag.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 505)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 506) The following command will install the driver module with the same
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 507) options as above::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 508)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 509) modprobe sym53c8xx cmd_per_lun=4 sync=10 debug=0x200
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 510)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 511) 10.2 Available arguments
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 512) ------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 513)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 514) 10.2.1 Default number of tagged commands
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 515) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 516) - cmd_per_lun=0 (or cmd_per_lun=1) tagged command queuing disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 517) - cmd_per_lun=#tags (#tags > 1) tagged command queuing enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 518)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 519) #tags will be truncated to the max queued commands configuration parameter.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 520)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 521) 10.2.2 Burst max
^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) ========== ======================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 525) burst=0 burst disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 526) burst=255 get burst length from initial IO register settings.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 527) burst=#x burst enabled (1<<#x burst transfers max)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 528)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 529) #x is an integer value which is log base 2 of the burst
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 530) transfers max.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 531) ========== ======================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 532)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 533) By default the driver uses the maximum value supported by the chip.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 534)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 535) 10.2.3 LED support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 536) ^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 537)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 538) ===== ===================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 539) led=1 enable LED support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 540) led=0 disable LED support
^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) Do not enable LED support if your scsi board does not use SDMS BIOS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 544) (See 'Configuration parameters')
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 545)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 546) 10.2.4 Differential mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 547) ^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 548)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 549) ====== =================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 550) diff=0 never set up diff mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 551) diff=1 set up diff mode if BIOS set it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 552) diff=2 always set up diff mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 553) diff=3 set diff mode if GPIO3 is not set
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 554) ====== =================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 555)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 556) 10.2.5 IRQ mode
^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) ====== ================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 560) irqm=0 always open drain
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 561) irqm=1 same as initial settings (assumed BIOS settings)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 562) irqm=2 always totem pole
^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) 10.2.6 Check SCSI BUS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 566) ^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 567)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 568) buschk=<option bits>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 569)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 570) Available option bits:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 571)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 572) === ================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 573) 0x0 No check.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 574) 0x1 Check and do not attach the controller on error.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 575) 0x2 Check and just warn on error.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 576) === ================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 577)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 578) 10.2.7 Suggest a default SCSI id for hosts
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 579) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 580)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 581) ========== ==========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 582) hostid=255 no id suggested.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 583) hostid=#x (0 < x < 7) x suggested for hosts SCSI id.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 584) ========== ==========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 585)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 586) If a host SCSI id is available from the NVRAM, the driver will ignore
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 587) any value suggested as boot option. Otherwise, if a suggested value
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 588) different from 255 has been supplied, it will use it. Otherwise, it will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 589) try to deduce the value previously set in the hardware and use value
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 590) 7 if the hardware value is zero.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 591)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 592) 10.2.8 Verbosity 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) ====== ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 596) verb=0 minimal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 597) verb=1 normal
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 598) verb=2 too much
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 599) ====== ========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 600)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 601) 10.2.9 Debug mode
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 602) ^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 603)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 604) ========= ====================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 605) debug=0 clear debug flags
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 606) debug=#x set debug flags
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 607)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 608) #x is an integer value combining the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 609) following power-of-2 values:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 610)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 611) ============= ======
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 612) DEBUG_ALLOC 0x1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 613) DEBUG_PHASE 0x2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 614) DEBUG_POLL 0x4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 615) DEBUG_QUEUE 0x8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 616) DEBUG_RESULT 0x10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 617) DEBUG_SCATTER 0x20
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 618) DEBUG_SCRIPT 0x40
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 619) DEBUG_TINY 0x80
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 620) DEBUG_TIMING 0x100
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 621) DEBUG_NEGO 0x200
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 622) DEBUG_TAGS 0x400
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 623) DEBUG_FREEZE 0x800
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 624) DEBUG_RESTART 0x1000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 625) ============= ======
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 626) ========= ====================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 627)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 628) You can play safely with DEBUG_NEGO. However, some of these flags may
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 629) generate bunches of syslog messages.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 630)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 631) 10.2.10 Settle delay
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 632) ^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 633)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 634) ======== ===================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 635) settle=n delay for n seconds
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 636) ======== ===================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 637)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 638) After a bus reset, the driver will delay for n seconds before talking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 639) to any device on the bus. The default is 3 seconds and safe mode will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 640) default it to 10.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 641)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 642) 10.2.11 Serial NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 643) ^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 644)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 645) .. Note:: option not currently implemented.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 646)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 647) ======= =========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 648) nvram=n do not look for serial NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 649) nvram=y test controllers for onboard serial NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 650) ======= =========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 651)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 652) (alternate binary form)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 653)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 654) nvram=<bits options>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 655)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 656) ==== =================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 657) 0x01 look for NVRAM (equivalent to nvram=y)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 658) 0x02 ignore NVRAM "Synchronous negotiation" parameters for all devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 659) 0x04 ignore NVRAM "Wide negotiation" parameter for all devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 660) 0x08 ignore NVRAM "Scan at boot time" parameter for all devices
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 661) 0x80 also attach controllers set to OFF in the NVRAM (sym53c8xx only)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 662) ==== =================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 663)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 664) 10.2.12 Exclude a host from being attached
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 665) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 666)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 667) excl=<io_address>,...
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 668)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 669) Prevent host at a given io address from being attached.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 670) For example 'excl=0xb400,0xc000' indicate to the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 671) driver not to attach hosts at address 0xb400 and 0xc000.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 672)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 673) 10.3 Converting from old style options
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 674) --------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 675)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 676) Previously, the sym2 driver accepted arguments of the form::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 677)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 678) sym53c8xx=tags:4,sync:10,debug:0x200
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 679)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 680) As a result of the new module parameters, this is no longer available.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 681) Most of the options have remained the same, but tags has become
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 682) cmd_per_lun to reflect its different purposes. The sample above would
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 683) be specified as::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 684)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 685) modprobe sym53c8xx cmd_per_lun=4 sync=10 debug=0x200
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 686)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 687) or on the kernel boot line as::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 688)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 689) sym53c8xx.cmd_per_lun=4 sym53c8xx.sync=10 sym53c8xx.debug=0x200
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 690)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 691) 10.4 SCSI BUS checking boot option
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 692) ----------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 693)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 694) When this option is set to a non-zero value, the driver checks SCSI lines
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 695) logic state, 100 micro-seconds after having asserted the SCSI RESET line.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 696) The driver just reads SCSI lines and checks all lines read FALSE except RESET.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 697) Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 698) RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 699) Unfortunately, the following common SCSI BUS problems are not detected:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 700)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 701) - Only 1 terminator installed.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 702) - Misplaced terminators.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 703) - Bad quality terminators.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 704)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 705) On the other hand, either bad cabling, broken devices, not conformant
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 706) devices, ... may cause a SCSI signal to be wrong when te driver reads it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 707)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 708) 15. SCSI problem troubleshooting
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 709) ================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 710)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 711) 15.1 Problem tracking
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 712) ---------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 713)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 714) Most SCSI problems are due to a non conformant SCSI bus or too buggy
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 715) devices. If unfortunately you have SCSI problems, you can check the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 716) following things:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 717)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 718) - SCSI bus cables
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 719) - terminations at both end of the SCSI chain
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 720) - linux syslog messages (some of them may help you)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 721)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 722) If you do not find the source of problems, you can configure the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 723) driver or devices in the NVRAM with minimal features.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 724)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 725) - only asynchronous data transfers
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 726) - tagged commands disabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 727) - disconnections not allowed
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 728)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 729) Now, if your SCSI bus is ok, your system has every chance to work
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 730) with this safe configuration but performances will not be optimal.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 731)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 732) If it still fails, then you can send your problem description to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 733) appropriate mailing lists or news-groups. Send me a copy in order to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 734) be sure I will receive it. Obviously, a bug in the driver code is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 735) possible.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 736)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 737) My current email address: Gerard Roudier <groudier@free.fr>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 738)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 739) Allowing disconnections is important if you use several devices on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 740) your SCSI bus but often causes problems with buggy devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 741) Synchronous data transfers increases throughput of fast devices like
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 742) hard disks. Good SCSI hard disks with a large cache gain advantage of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 743) tagged commands queuing.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 744)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 745) 15.2 Understanding hardware error reports
^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) When the driver detects an unexpected error condition, it may display a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 749) message of the following pattern::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 750)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 751) sym0:1: ERROR (0:48) (1-21-65) (f/95/0) @ (script 7c0:19000000).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 752) sym0: script cmd = 19000000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 753) sym0: 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 754)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 755) Some fields in such a message may help you understand the cause of the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 756) problem, as follows::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 757)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 758) sym0:1: ERROR (0:48) (1-21-65) (f/95/0) @ (script 7c0:19000000).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 759) .....A.........B.C....D.E..F....G.H..I.......J.....K...L.......
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 760)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 761) Field A : target number.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 762) SCSI ID of the device the controller was talking with at the moment the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 763) error occurs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 764)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 765) Field B : DSTAT io register (DMA STATUS)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 766) ======== =============================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 767) Bit 0x40 MDPE Master Data Parity Error
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 768) Data parity error detected on the PCI BUS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 769) Bit 0x20 BF Bus Fault
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 770) PCI bus fault condition detected
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 771) Bit 0x01 IID Illegal Instruction Detected
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 772) Set by the chip when it detects an Illegal Instruction format
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 773) on some condition that makes an instruction illegal.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 774) Bit 0x80 DFE Dma Fifo Empty
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 775) Pure status bit that does not indicate an error.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 776) ======== =============================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 777)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 778) If the reported DSTAT value contains a combination of MDPE (0x40),
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 779) BF (0x20), then the cause may be likely due to a PCI BUS problem.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 780)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 781) Field C : SIST io register (SCSI Interrupt Status)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 782) ======== ==================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 783) Bit 0x08 SGE SCSI GROSS ERROR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 784) Indicates that the chip detected a severe error condition
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 785) on the SCSI BUS that prevents the SCSI protocol from functioning
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 786) properly.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 787) Bit 0x04 UDC Unexpected Disconnection
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 788) Indicates that the device released the SCSI BUS when the chip
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 789) was not expecting this to happen. A device may behave so to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 790) indicate the SCSI initiator that an error condition not reportable using the SCSI protocol has occurred.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 791) Bit 0x02 RST SCSI BUS Reset
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 792) Generally SCSI targets do not reset the SCSI BUS, although any
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 793) device on the BUS can reset it at any time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 794) Bit 0x01 PAR Parity
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 795) SCSI parity error detected.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 796) ======== ==================================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 797)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 798) On a faulty SCSI BUS, any error condition among SGE (0x08), UDC (0x04) and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 799) PAR (0x01) may be detected by the chip. If your SCSI system sometimes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 800) encounters such error conditions, especially SCSI GROSS ERROR, then a SCSI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 801) BUS problem is likely the cause of these errors.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 802)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 803) 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 804) that contains some minimal comments on IO register bits.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 805)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 806) Field D : SOCL Scsi Output Control Latch
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 807) This register reflects the state of the SCSI control lines the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 808) chip want to drive or compare against.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 809) Field E : SBCL Scsi Bus Control Lines
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 810) Actual value of control lines on the SCSI BUS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 811) Field F : SBDL Scsi Bus Data Lines
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 812) Actual value of data lines on the SCSI BUS.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 813) Field G : SXFER SCSI Transfer
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 814) Contains the setting of the Synchronous Period for output and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 815) the current Synchronous offset (offset 0 means asynchronous).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 816) Field H : SCNTL3 Scsi Control Register 3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 817) Contains the setting of timing values for both asynchronous and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 818) synchronous data transfers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 819) Field I : SCNTL4 Scsi Control Register 4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 820) Only meaningful for 53C1010 Ultra3 controllers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 821)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 822) Understanding Fields J, K, L and dumps requires to have good knowledge of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 823) SCSI standards, chip cores functionnals and internal driver data structures.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 824) You are not required to decode and understand them, unless you want to help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 825) maintain the driver code.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 826)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 827) 17. Serial NVRAM (added by Richard Waltham: dormouse@farsrobt.demon.co.uk)
^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) 17.1 Features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 831) -------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 832)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 833) Enabling serial NVRAM support enables detection of the serial NVRAM included
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 834) on Symbios and some Symbios compatible host adaptors, and Tekram boards. The
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 835) serial NVRAM is used by Symbios and Tekram to hold set up parameters for the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 836) host adaptor and its attached drives.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 837)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 838) The Symbios NVRAM also holds data on the boot order of host adaptors in a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 839) system with more than one host adaptor. This information is no longer used
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 840) as it's fundamentally incompatible with the hotplug PCI model.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 841)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 842) Tekram boards using Symbios chips, DC390W/F/U, which have NVRAM are detected
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 843) and this is used to distinguish between Symbios compatible and Tekram host
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 844) adaptors. This is used to disable the Symbios compatible "diff" setting
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 845) incorrectly set on Tekram boards if the CONFIG_SCSI_53C8XX_SYMBIOS_COMPAT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 846) configuration parameter is set enabling both Symbios and Tekram boards to be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 847) used together with the Symbios cards using all their features, including
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 848) "diff" support. ("led pin" support for Symbios compatible cards can remain
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 849) enabled when using Tekram cards. It does nothing useful for Tekram host
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 850) adaptors but does not cause problems either.)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 851)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 852) The parameters the driver is able to get from the NVRAM depend on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 853) data format used, as follow:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 854)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 855) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 856) | |Tekram format |Symbios format|
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 857) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 858) |General and host parameters | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 859) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 860) | * Boot order | N | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 861) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 862) | * Host SCSI ID | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 863) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 864) | * SCSI parity checking | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 865) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 866) | * Verbose boot messages | N | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 867) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 868) |SCSI devices parameters |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 869) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 870) | * Synchronous transfer speed | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 871) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 872) | * Wide 16 / Narrow | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 873) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 874) | * Tagged Command Queuing | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 875) | enabled | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 876) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 877) | * Disconnections enabled | Y | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 878) +-------------------------------+------------------+--------------+
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 879) | * Scan at boot time | N | Y |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 880) +-------------------------------+------------------+--------------+
^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) In order to speed up the system boot, for each device configured without
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 884) the "scan at boot time" option, the driver forces an error on the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 885) first TEST UNIT READY command received for this device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 886)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 887)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 888) 17.2 Symbios NVRAM layout
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 889) -------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 890)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 891) typical data at NVRAM address 0x100 (53c810a NVRAM)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 892)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 893) 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 894) 64 01
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 895) 8e 0b
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 896)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 897) 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 898)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 899) 04 00 0f 00 00 10 00 50 00 00 01 00 00 62
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 900) 04 00 03 00 00 10 00 58 00 00 01 00 00 63
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 901) 04 00 01 00 00 10 00 48 00 00 01 00 00 61
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 902) 00 00 00 00 00 00 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 903)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 904) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 905) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 906) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 907) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 908) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 909) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 910) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 911) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 912)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 913) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 914) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 915) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 916) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 917) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 918) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 919) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 920) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 921)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 922) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 923) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 924) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 925) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 926) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 927) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 928) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 929) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 930)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 931) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 932) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 933) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 934) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 935) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 936) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 937) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 938) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 939)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 940) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 941) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 942) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 943)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 944) fe fe
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 945) 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 946) 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 947)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 948) NVRAM layout details
^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) NVRAM Address
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 952) ============= =================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 953) 0x000-0x0ff not used
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 954) 0x100-0x26f initialised data
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 955) 0x270-0x7ff not used
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 956) ============= =================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 957)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 958) general layout::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 959)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 960) header - 6 bytes,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 961) data - 356 bytes (checksum is byte sum of this data)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 962) trailer - 6 bytes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 963) ---
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 964) total 368 bytes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 965)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 966) data area layout::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 967)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 968) controller set up - 20 bytes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 969) boot configuration - 56 bytes (4x14 bytes)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 970) device set up - 128 bytes (16x8 bytes)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 971) unused (spare?) - 152 bytes (19x8 bytes)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 972) ---
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 973) total 356 bytes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 974)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 975) header::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 976)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 977) 00 00 - ?? start marker
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 978) 64 01 - byte count (lsb/msb excludes header/trailer)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 979) 8e 0b - checksum (lsb/msb excludes header/trailer)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 980)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 981) controller set up::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 982)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 983) 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 984) | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 985) | | | -- host ID
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 986) | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 987) | | --Removable Media Support
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 988) | | 0x00 = none
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 989) | | 0x01 = Bootable Device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 990) | | 0x02 = All with Media
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 991) | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 992) | --flag bits 2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 993) | 0x00000001= scan order hi->low
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 994) | (default 0x00 - scan low->hi)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 995) --flag bits 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 996) 0x00000001 scam enable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 997) 0x00000010 parity enable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 998) 0x00000100 verbose boot msgs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 999)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1000) remaining bytes unknown - they do not appear to change in my
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1001) current set up for any of the controllers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1002)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1003) default set up is identical for 53c810a and 53c875 NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1004) (Removable Media added Symbios BIOS version 4.09)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1005)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1006) boot configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1007)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1008) boot order set by order of the devices in this table::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1009)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1010) 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 1011) 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 1012) 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 1013) 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 1014) | | | | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1015) | | | | | | ---- PCI io port adr
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1016) | | | | | --0x01 init/scan at boot time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1017) | | | | --PCI device/function number (0xdddddfff)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1018) | | ----- ?? PCI vendor ID (lsb/msb)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1019) ----PCI device ID (lsb/msb)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1020)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1021) ?? use of this data is a guess but seems reasonable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1022)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1023) remaining bytes unknown - they do not appear to change in my
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1024) current set up
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1025)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1026) default set up is identical for 53c810a and 53c875 NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1027)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1028) device set up (up to 16 devices - includes controller)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1029)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1030) 0f 00 08 08 64 00 0a 00 - id 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1031) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1032) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1033) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1034) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1035) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1036) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1037) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1038)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1039) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1040) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1041) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1042) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1043) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1044) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1045) 0f 00 08 08 64 00 0a 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1046) 0f 00 08 08 64 00 0a 00 - id 15
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1047) | | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1048) | | | | ----timeout (lsb/msb)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1049) | | | --synch period (0x?? 40 Mtrans/sec- fast 40) (probably 0x28)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1050) | | | (0x30 20 Mtrans/sec- fast 20)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1051) | | | (0x64 10 Mtrans/sec- fast )
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1052) | | | (0xc8 5 Mtrans/sec)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1053) | | | (0x00 asynchronous)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1054) | | -- ?? max sync offset (0x08 in NVRAM on 53c810a)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1055) | | (0x10 in NVRAM on 53c875)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1056) | --device bus width (0x08 narrow)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1057) | (0x10 16 bit wide)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1058) --flag bits
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1059) 0x00000001 - disconnect enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1060) 0x00000010 - scan at boot time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1061) 0x00000100 - scan luns
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1062) 0x00001000 - queue tags enabled
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1063)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1064) remaining bytes unknown - they do not appear to change in my
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1065) current set up
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1066)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1067) ?? use of this data is a guess but seems reasonable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1068) (but it could be max bus width)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1069)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1070) default set up for 53c810a NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1071) default set up for 53c875 NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1072)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1073) - bus width - 0x10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1074) - sync offset ? - 0x10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1075) - sync period - 0x30
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1076)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1077) ?? spare device space (32 bit bus ??)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1078)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1079) 00 00 00 00 00 00 00 00 (19x8bytes)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1080) .
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1081) .
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1082) 00 00 00 00 00 00 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1083)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1084) default set up is identical for 53c810a and 53c875 NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1085)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1086) trailer::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1087)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1088) fe fe - ? end marker ?
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1089) 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1090) 00 00
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1091)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1092) default set up is identical for 53c810a and 53c875 NVRAM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1093)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1094) 17.3 Tekram NVRAM layout
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1095) ------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1096)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1097) nvram 64x16 (1024 bit)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1098)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1099) Drive settings::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1100)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1101) Drive ID 0-15 (addr 0x0yyyy0 = device setup, yyyy = ID)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1102) (addr 0x0yyyy1 = 0x0000)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1103)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1104) 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 1105) | | | | | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1106) | | | | | | | | ----- parity check 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1107) | | | | | | | | 1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1108) | | | | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1109) | | | | | | | ------- sync neg 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1110) | | | | | | | 1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1111) | | | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1112) | | | | | | --------- disconnect 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1113) | | | | | | 1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1114) | | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1115) | | | | | ----------- start cmd 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1116) | | | | | 1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1117) | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1118) | | | | -------------- tagged cmds 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1119) | | | | 1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1120) | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1121) | | | ---------------- wide neg 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1122) | | | 1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1123) | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1124) --------------------------- sync rate 0 - 10.0 Mtrans/sec
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1125) 1 - 8.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1126) 2 - 6.6
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1127) 3 - 5.7
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1128) 4 - 5.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1129) 5 - 4.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1130) 6 - 3.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1131) 7 - 2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1132) 7 - 2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1133) 8 - 20.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1134) 9 - 16.7
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1135) a - 13.9
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1136) b - 11.9
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1137)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1138) Global settings
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1139)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1140) Host flags 0 (addr 0x100000, 32)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1141)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1142) 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 1143) | | | | | | | | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1144) | | | | | | | | ----------- host ID 0x00 - 0x0f
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1145) | | | | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1146) | | | | | | | ----------------------- support for 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1147) | | | | | | | > 2 drives 1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1148) | | | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1149) | | | | | | ------------------------- support drives 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1150) | | | | | | > 1Gbytes 1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1151) | | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1152) | | | | | --------------------------- bus reset on 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1153) | | | | | power on 1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1154) | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1155) | | | | ----------------------------- active neg 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1156) | | | | 1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1157) | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1158) | | | -------------------------------- imm seek 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1159) | | | 1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1160) | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1161) | | ---------------------------------- scan luns 0 - off
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1162) | | 1 - on
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1163) | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1164) -------------------------------------- removable 0 - disable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1165) as BIOS dev 1 - boot device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1166) 2 - all
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1167)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1168) Host flags 1 (addr 0x100001, 33)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1169)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1170) 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 1171) | | | | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1172) | | | --------- boot delay 0 - 3 sec
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1173) | | | 1 - 5
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1174) | | | 2 - 10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1175) | | | 3 - 20
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1176) | | | 4 - 30
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1177) | | | 5 - 60
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1178) | | | 6 - 120
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1179) | | |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1180) --------------------------- max tag cmds 0 - 2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1181) 1 - 4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1182) 2 - 8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1183) 3 - 16
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1184) 4 - 32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1185)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1186) Host flags 2 (addr 0x100010, 34)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1187)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1188) 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 1189) |
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1190) ----- F2/F6 enable 0 - off ???
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1191) 1 - on ???
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1192)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1193) checksum (addr 0x111111)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1194)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1195) checksum = 0x1234 - (sum addr 0-63)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1196)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1197) ----------------------------------------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1198)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1199) default nvram data::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1200)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1201) 0x0037 0x0000 0x0037 0x0000 0x0037 0x0000 0x0037 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1202) 0x0037 0x0000 0x0037 0x0000 0x0037 0x0000 0x0037 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1203) 0x0037 0x0000 0x0037 0x0000 0x0037 0x0000 0x0037 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1204) 0x0037 0x0000 0x0037 0x0000 0x0037 0x0000 0x0037 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1205)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1206) 0x0f07 0x0400 0x0001 0x0000 0x0000 0x0000 0x0000 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1207) 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1208) 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1209) 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0xfbbc
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags