ncr53c8xx.txt 72 KB

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