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