BusLogic.txt 26 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566
  1. BusLogic MultiMaster and FlashPoint SCSI Driver for Linux
  2. Version 2.0.15 for Linux 2.0
  3. Version 2.1.15 for Linux 2.1
  4. PRODUCTION RELEASE
  5. 17 August 1998
  6. Leonard N. Zubkoff
  7. Dandelion Digital
  8. lnz@dandelion.com
  9. Copyright 1995-1998 by Leonard N. Zubkoff <lnz@dandelion.com>
  10. INTRODUCTION
  11. BusLogic, Inc. designed and manufactured a variety of high performance SCSI
  12. host adapters which share a common programming interface across a diverse
  13. collection of bus architectures by virtue of their MultiMaster ASIC technology.
  14. BusLogic was acquired by Mylex Corporation in February 1996, but the products
  15. supported by this driver originated under the BusLogic name and so that name is
  16. retained in the source code and documentation.
  17. This driver supports all present BusLogic MultiMaster Host Adapters, and should
  18. support any future MultiMaster designs with little or no modification. More
  19. recently, BusLogic introduced the FlashPoint Host Adapters, which are less
  20. costly and rely on the host CPU, rather than including an onboard processor.
  21. Despite not having an onboard CPU, the FlashPoint Host Adapters perform very
  22. well and have very low command latency. BusLogic has recently provided me with
  23. the FlashPoint Driver Developer's Kit, which comprises documentation and freely
  24. redistributable source code for the FlashPoint SCCB Manager. The SCCB Manager
  25. is the library of code that runs on the host CPU and performs functions
  26. analogous to the firmware on the MultiMaster Host Adapters. Thanks to their
  27. having provided the SCCB Manager, this driver now supports the FlashPoint Host
  28. Adapters as well.
  29. My primary goals in writing this completely new BusLogic driver for Linux are
  30. to achieve the full performance that BusLogic SCSI Host Adapters and modern
  31. SCSI peripherals are capable of, and to provide a highly robust driver that can
  32. be depended upon for high performance mission critical applications. All of
  33. the major performance features can be configured from the Linux kernel command
  34. line or at module initialization time, allowing individual installations to
  35. tune driver performance and error recovery to their particular needs.
  36. The latest information on Linux support for BusLogic SCSI Host Adapters, as
  37. well as the most recent release of this driver and the latest firmware for the
  38. BT-948/958/958D, will always be available from my Linux Home Page at URL
  39. "http://www.dandelion.com/Linux/".
  40. Bug reports should be sent via electronic mail to "lnz@dandelion.com". Please
  41. include with the bug report the complete configuration messages reported by the
  42. driver and SCSI subsystem at startup, along with any subsequent system messages
  43. relevant to SCSI operations, and a detailed description of your system's
  44. hardware configuration.
  45. Mylex has been an excellent company to work with and I highly recommend their
  46. products to the Linux community. In November 1995, I was offered the
  47. opportunity to become a beta test site for their latest MultiMaster product,
  48. the BT-948 PCI Ultra SCSI Host Adapter, and then again for the BT-958 PCI Wide
  49. Ultra SCSI Host Adapter in January 1996. This was mutually beneficial since
  50. Mylex received a degree and kind of testing that their own testing group cannot
  51. readily achieve, and the Linux community has available high performance host
  52. adapters that have been well tested with Linux even before being brought to
  53. market. This relationship has also given me the opportunity to interact
  54. directly with their technical staff, to understand more about the internal
  55. workings of their products, and in turn to educate them about the needs and
  56. potential of the Linux community.
  57. More recently, Mylex has reaffirmed the company's interest in supporting the
  58. Linux community, and I am now working on a Linux driver for the DAC960 PCI RAID
  59. Controllers. Mylex's interest and support is greatly appreciated.
  60. Unlike some other vendors, if you contact Mylex Technical Support with a
  61. problem and are running Linux, they will not tell you that your use of their
  62. products is unsupported. Their latest product marketing literature even states
  63. "Mylex SCSI host adapters are compatible with all major operating systems
  64. including: ... Linux ...".
  65. Mylex Corporation is located at 34551 Ardenwood Blvd., Fremont, California
  66. 94555, USA and can be reached at 510/796-6100 or on the World Wide Web at
  67. http://www.mylex.com. Mylex HBA Technical Support can be reached by electronic
  68. mail at techsup@mylex.com, by Voice at 510/608-2400, or by FAX at 510/745-7715.
  69. Contact information for offices in Europe and Japan is available on the Web
  70. site.
  71. DRIVER FEATURES
  72. o Configuration Reporting and Testing
  73. During system initialization, the driver reports extensively on the host
  74. adapter hardware configuration, including the synchronous transfer parameters
  75. requested and negotiated with each target device. AutoSCSI settings for
  76. Synchronous Negotiation, Wide Negotiation, and Disconnect/Reconnect are
  77. reported for each target device, as well as the status of Tagged Queuing.
  78. If the same setting is in effect for all target devices, then a single word
  79. or phrase is used; otherwise, a letter is provided for each target device to
  80. indicate the individual status. The following examples
  81. should clarify this reporting format:
  82. Synchronous Negotiation: Ultra
  83. Synchronous negotiation is enabled for all target devices and the host
  84. adapter will attempt to negotiate for 20.0 mega-transfers/second.
  85. Synchronous Negotiation: Fast
  86. Synchronous negotiation is enabled for all target devices and the host
  87. adapter will attempt to negotiate for 10.0 mega-transfers/second.
  88. Synchronous Negotiation: Slow
  89. Synchronous negotiation is enabled for all target devices and the host
  90. adapter will attempt to negotiate for 5.0 mega-transfers/second.
  91. Synchronous Negotiation: Disabled
  92. Synchronous negotiation is disabled and all target devices are limited to
  93. asynchronous operation.
  94. Synchronous Negotiation: UFSNUUU#UUUUUUUU
  95. Synchronous negotiation to Ultra speed is enabled for target devices 0
  96. and 4 through 15, to Fast speed for target device 1, to Slow speed for
  97. target device 2, and is not permitted to target device 3. The host
  98. adapter's SCSI ID is represented by the "#".
  99. The status of Wide Negotiation, Disconnect/Reconnect, and Tagged Queuing
  100. are reported as "Enabled", Disabled", or a sequence of "Y" and "N" letters.
  101. o Performance Features
  102. BusLogic SCSI Host Adapters directly implement SCSI-2 Tagged Queuing, and so
  103. support has been included in the driver to utilize tagged queuing with any
  104. target devices that report having the tagged queuing capability. Tagged
  105. queuing allows for multiple outstanding commands to be issued to each target
  106. device or logical unit, and can improve I/O performance substantially. In
  107. addition, BusLogic's Strict Round Robin Mode is used to optimize host adapter
  108. performance, and scatter/gather I/O can support as many segments as can be
  109. effectively utilized by the Linux I/O subsystem. Control over the use of
  110. tagged queuing for each target device as well as individual selection of the
  111. tagged queue depth is available through driver options provided on the kernel
  112. command line or at module initialization time. By default, the queue depth
  113. is determined automatically based on the host adapter's total queue depth and
  114. the number, type, speed, and capabilities of the target devices found. In
  115. addition, tagged queuing is automatically disabled whenever the host adapter
  116. firmware version is known not to implement it correctly, or whenever a tagged
  117. queue depth of 1 is selected. Tagged queuing is also disabled for individual
  118. target devices if disconnect/reconnect is disabled for that device.
  119. o Robustness Features
  120. The driver implements extensive error recovery procedures. When the higher
  121. level parts of the SCSI subsystem request that a timed out command be reset,
  122. a selection is made between a full host adapter hard reset and SCSI bus reset
  123. versus sending a bus device reset message to the individual target device
  124. based on the recommendation of the SCSI subsystem. Error recovery strategies
  125. are selectable through driver options individually for each target device,
  126. and also include sending a bus device reset to the specific target device
  127. associated with the command being reset, as well as suppressing error
  128. recovery entirely to avoid perturbing an improperly functioning device. If
  129. the bus device reset error recovery strategy is selected and sending a bus
  130. device reset does not restore correct operation, the next command that is
  131. reset will force a full host adapter hard reset and SCSI bus reset. SCSI bus
  132. resets caused by other devices and detected by the host adapter are also
  133. handled by issuing a soft reset to the host adapter and re-initialization.
  134. Finally, if tagged queuing is active and more than one command reset occurs
  135. in a 10 minute interval, or if a command reset occurs within the first 10
  136. minutes of operation, then tagged queuing will be disabled for that target
  137. device. These error recovery options improve overall system robustness by
  138. preventing individual errant devices from causing the system as a whole to
  139. lock up or crash, and thereby allowing a clean shutdown and restart after the
  140. offending component is removed.
  141. o PCI Configuration Support
  142. On PCI systems running kernels compiled with PCI BIOS support enabled, this
  143. driver will interrogate the PCI configuration space and use the I/O port
  144. addresses assigned by the system BIOS, rather than the ISA compatible I/O
  145. port addresses. The ISA compatible I/O port address is then disabled by the
  146. driver. On PCI systems it is also recommended that the AutoSCSI utility be
  147. used to disable the ISA compatible I/O port entirely as it is not necessary.
  148. The ISA compatible I/O port is disabled by default on the BT-948/958/958D.
  149. o /proc File System Support
  150. Copies of the host adapter configuration information together with updated
  151. data transfer and error recovery statistics are available through the
  152. /proc/scsi/BusLogic/<N> interface.
  153. o Shared Interrupts Support
  154. On systems that support shared interrupts, any number of BusLogic Host
  155. Adapters may share the same interrupt request channel.
  156. SUPPORTED HOST ADAPTERS
  157. The following list comprises the supported BusLogic SCSI Host Adapters as of
  158. the date of this document. It is recommended that anyone purchasing a BusLogic
  159. Host Adapter not in the following table contact the author beforehand to verify
  160. that it is or will be supported.
  161. FlashPoint Series PCI Host Adapters:
  162. FlashPoint LT (BT-930) Ultra SCSI-3
  163. FlashPoint LT (BT-930R) Ultra SCSI-3 with RAIDPlus
  164. FlashPoint LT (BT-920) Ultra SCSI-3 (BT-930 without BIOS)
  165. FlashPoint DL (BT-932) Dual Channel Ultra SCSI-3
  166. FlashPoint DL (BT-932R) Dual Channel Ultra SCSI-3 with RAIDPlus
  167. FlashPoint LW (BT-950) Wide Ultra SCSI-3
  168. FlashPoint LW (BT-950R) Wide Ultra SCSI-3 with RAIDPlus
  169. FlashPoint DW (BT-952) Dual Channel Wide Ultra SCSI-3
  170. FlashPoint DW (BT-952R) Dual Channel Wide Ultra SCSI-3 with RAIDPlus
  171. MultiMaster "W" Series Host Adapters:
  172. BT-948 PCI Ultra SCSI-3
  173. BT-958 PCI Wide Ultra SCSI-3
  174. BT-958D PCI Wide Differential Ultra SCSI-3
  175. MultiMaster "C" Series Host Adapters:
  176. BT-946C PCI Fast SCSI-2
  177. BT-956C PCI Wide Fast SCSI-2
  178. BT-956CD PCI Wide Differential Fast SCSI-2
  179. BT-445C VLB Fast SCSI-2
  180. BT-747C EISA Fast SCSI-2
  181. BT-757C EISA Wide Fast SCSI-2
  182. BT-757CD EISA Wide Differential Fast SCSI-2
  183. BT-545C ISA Fast SCSI-2
  184. BT-540CF ISA Fast SCSI-2
  185. MultiMaster "S" Series Host Adapters:
  186. BT-445S VLB Fast SCSI-2
  187. BT-747S EISA Fast SCSI-2
  188. BT-747D EISA Differential Fast SCSI-2
  189. BT-757S EISA Wide Fast SCSI-2
  190. BT-757D EISA Wide Differential Fast SCSI-2
  191. BT-545S ISA Fast SCSI-2
  192. BT-542D ISA Differential Fast SCSI-2
  193. BT-742A EISA SCSI-2 (742A revision H)
  194. BT-542B ISA SCSI-2 (542B revision H)
  195. MultiMaster "A" Series Host Adapters:
  196. BT-742A EISA SCSI-2 (742A revisions A - G)
  197. BT-542B ISA SCSI-2 (542B revisions A - G)
  198. AMI FastDisk Host Adapters that are true BusLogic MultiMaster clones are also
  199. supported by this driver.
  200. BusLogic SCSI Host Adapters are available packaged both as bare boards and as
  201. retail kits. The BT- model numbers above refer to the bare board packaging.
  202. The retail kit model numbers are found by replacing BT- with KT- in the above
  203. list. The retail kit includes the bare board and manual as well as cabling and
  204. driver media and documentation that are not provided with bare boards.
  205. FLASHPOINT INSTALLATION NOTES
  206. o RAIDPlus Support
  207. FlashPoint Host Adapters now include RAIDPlus, Mylex's bootable software
  208. RAID. RAIDPlus is not supported on Linux, and there are no plans to support
  209. it. The MD driver in Linux 2.0 provides for concatenation (LINEAR) and
  210. striping (RAID-0), and support for mirroring (RAID-1), fixed parity (RAID-4),
  211. and distributed parity (RAID-5) is available separately. The built-in Linux
  212. RAID support is generally more flexible and is expected to perform better
  213. than RAIDPlus, so there is little impetus to include RAIDPlus support in the
  214. BusLogic driver.
  215. o Enabling UltraSCSI Transfers
  216. FlashPoint Host Adapters ship with their configuration set to "Factory
  217. Default" settings that are conservative and do not allow for UltraSCSI speed
  218. to be negotiated. This results in fewer problems when these host adapters
  219. are installed in systems with cabling or termination that is not sufficient
  220. for UltraSCSI operation, or where existing SCSI devices do not properly
  221. respond to synchronous transfer negotiation for UltraSCSI speed. AutoSCSI
  222. may be used to load "Optimum Performance" settings which allow UltraSCSI
  223. speed to be negotiated with all devices, or UltraSCSI speed can be enabled on
  224. an individual basis. It is recommended that SCAM be manually disabled after
  225. the "Optimum Performance" settings are loaded.
  226. BT-948/958/958D INSTALLATION NOTES
  227. The BT-948/958/958D PCI Ultra SCSI Host Adapters have some features which may
  228. require attention in some circumstances when installing Linux.
  229. o PCI I/O Port Assignments
  230. When configured to factory default settings, the BT-948/958/958D will only
  231. recognize the PCI I/O port assignments made by the motherboard's PCI BIOS.
  232. The BT-948/958/958D will not respond to any of the ISA compatible I/O ports
  233. that previous BusLogic SCSI Host Adapters respond to. This driver supports
  234. the PCI I/O port assignments, so this is the preferred configuration.
  235. However, if the obsolete BusLogic driver must be used for any reason, such as
  236. a Linux distribution that does not yet use this driver in its boot kernel,
  237. BusLogic has provided an AutoSCSI configuration option to enable a legacy ISA
  238. compatible I/O port.
  239. To enable this backward compatibility option, invoke the AutoSCSI utility via
  240. Ctrl-B at system startup and select "Adapter Configuration", "View/Modify
  241. Configuration", and then change the "ISA Compatible Port" setting from
  242. "Disable" to "Primary" or "Alternate". Once this driver has been installed,
  243. the "ISA Compatible Port" option should be set back to "Disable" to avoid
  244. possible future I/O port conflicts. The older BT-946C/956C/956CD also have
  245. this configuration option, but the factory default setting is "Primary".
  246. o PCI Slot Scanning Order
  247. In systems with multiple BusLogic PCI Host Adapters, the order in which the
  248. PCI slots are scanned may appear reversed with the BT-948/958/958D as
  249. compared to the BT-946C/956C/956CD. For booting from a SCSI disk to work
  250. correctly, it is necessary that the host adapter's BIOS and the kernel agree
  251. on which disk is the boot device, which requires that they recognize the PCI
  252. host adapters in the same order. The motherboard's PCI BIOS provides a
  253. standard way of enumerating the PCI host adapters, which is used by the Linux
  254. kernel. Some PCI BIOS implementations enumerate the PCI slots in order of
  255. increasing bus number and device number, while others do so in the opposite
  256. direction.
  257. Unfortunately, Microsoft decided that Windows 95 would always enumerate the
  258. PCI slots in order of increasing bus number and device number regardless of
  259. the PCI BIOS enumeration, and requires that their scheme be supported by the
  260. host adapter's BIOS to receive Windows 95 certification. Therefore, the
  261. factory default settings of the BT-948/958/958D enumerate the host adapters
  262. by increasing bus number and device number. To disable this feature, invoke
  263. the AutoSCSI utility via Ctrl-B at system startup and select "Adapter
  264. Configuration", "View/Modify Configuration", press Ctrl-F10, and then change
  265. the "Use Bus And Device # For PCI Scanning Seq." option to OFF.
  266. This driver will interrogate the setting of the PCI Scanning Sequence option
  267. so as to recognize the host adapters in the same order as they are enumerated
  268. by the host adapter's BIOS.
  269. o Enabling UltraSCSI Transfers
  270. The BT-948/958/958D ship with their configuration set to "Factory Default"
  271. settings that are conservative and do not allow for UltraSCSI speed to be
  272. negotiated. This results in fewer problems when these host adapters are
  273. installed in systems with cabling or termination that is not sufficient for
  274. UltraSCSI operation, or where existing SCSI devices do not properly respond
  275. to synchronous transfer negotiation for UltraSCSI speed. AutoSCSI may be
  276. used to load "Optimum Performance" settings which allow UltraSCSI speed to be
  277. negotiated with all devices, or UltraSCSI speed can be enabled on an
  278. individual basis. It is recommended that SCAM be manually disabled after the
  279. "Optimum Performance" settings are loaded.
  280. DRIVER OPTIONS
  281. BusLogic Driver Options may be specified either via the Linux Kernel Command
  282. Line or via the Loadable Kernel Module Installation Facility. Driver Options
  283. for multiple host adapters may be specified either by separating the option
  284. strings by a semicolon, or by specifying multiple "BusLogic=" strings on the
  285. command line. Individual option specifications for a single host adapter are
  286. separated by commas. The Probing and Debugging Options apply to all host
  287. adapters whereas the remaining options apply individually only to the
  288. selected host adapter.
  289. The BusLogic Driver Probing Options comprise the following:
  290. IO:<integer>
  291. The "IO:" option specifies an ISA I/O Address to be probed for a non-PCI
  292. MultiMaster Host Adapter. If neither "IO:" nor "NoProbeISA" options are
  293. specified, then the standard list of BusLogic MultiMaster ISA I/O Addresses
  294. will be probed (0x330, 0x334, 0x230, 0x234, 0x130, and 0x134). Multiple
  295. "IO:" options may be specified to precisely determine the I/O Addresses to
  296. be probed, but the probe order will always follow the standard list.
  297. NoProbe
  298. The "NoProbe" option disables all probing and therefore no BusLogic Host
  299. Adapters will be detected.
  300. NoProbeISA
  301. The "NoProbeISA" option disables probing of the standard BusLogic ISA I/O
  302. Addresses and therefore only PCI MultiMaster and FlashPoint Host Adapters
  303. will be detected.
  304. NoProbePCI
  305. The "NoProbePCI" options disables the interrogation of PCI Configuration
  306. Space and therefore only ISA Multimaster Host Adapters will be detected, as
  307. well as PCI Multimaster Host Adapters that have their ISA Compatible I/O
  308. Port set to "Primary" or "Alternate".
  309. NoSortPCI
  310. The "NoSortPCI" option forces PCI MultiMaster Host Adapters to be
  311. enumerated in the order provided by the PCI BIOS, ignoring any setting of
  312. the AutoSCSI "Use Bus And Device # For PCI Scanning Seq." option.
  313. MultiMasterFirst
  314. The "MultiMasterFirst" option forces MultiMaster Host Adapters to be probed
  315. before FlashPoint Host Adapters. By default, if both FlashPoint and PCI
  316. MultiMaster Host Adapters are present, this driver will probe for
  317. FlashPoint Host Adapters first unless the BIOS primary disk is controlled
  318. by the first PCI MultiMaster Host Adapter, in which case MultiMaster Host
  319. Adapters will be probed first.
  320. FlashPointFirst
  321. The "FlashPointFirst" option forces FlashPoint Host Adapters to be probed
  322. before MultiMaster Host Adapters.
  323. The BusLogic Driver Tagged Queuing Options allow for explicitly specifying
  324. the Queue Depth and whether Tagged Queuing is permitted for each Target
  325. Device (assuming that the Target Device supports Tagged Queuing). The Queue
  326. Depth is the number of SCSI Commands that are allowed to be concurrently
  327. presented for execution (either to the Host Adapter or Target Device). Note
  328. that explicitly enabling Tagged Queuing may lead to problems; the option to
  329. enable or disable Tagged Queuing is provided primarily to allow disabling
  330. Tagged Queuing on Target Devices that do not implement it correctly. The
  331. following options are available:
  332. QueueDepth:<integer>
  333. The "QueueDepth:" or QD:" option specifies the Queue Depth to use for all
  334. Target Devices that support Tagged Queuing, as well as the maximum Queue
  335. Depth for devices that do not support Tagged Queuing. If no Queue Depth
  336. option is provided, the Queue Depth will be determined automatically based
  337. on the Host Adapter's Total Queue Depth and the number, type, speed, and
  338. capabilities of the detected Target Devices. For Host Adapters that
  339. require ISA Bounce Buffers, the Queue Depth is automatically set by default
  340. to BusLogic_TaggedQueueDepthBB or BusLogic_UntaggedQueueDepthBB to avoid
  341. excessive preallocation of DMA Bounce Buffer memory. Target Devices that
  342. do not support Tagged Queuing always have their Queue Depth set to
  343. BusLogic_UntaggedQueueDepth or BusLogic_UntaggedQueueDepthBB, unless a
  344. lower Queue Depth option is provided. A Queue Depth of 1 automatically
  345. disables Tagged Queuing.
  346. QueueDepth:[<integer>,<integer>...]
  347. The "QueueDepth:[...]" or "QD:[...]" option specifies the Queue Depth
  348. individually for each Target Device. If an <integer> is omitted, the
  349. associated Target Device will have its Queue Depth selected automatically.
  350. TaggedQueuing:Default
  351. The "TaggedQueuing:Default" or "TQ:Default" option permits Tagged Queuing
  352. based on the firmware version of the BusLogic Host Adapter and based on
  353. whether the Queue Depth allows queuing multiple commands.
  354. TaggedQueuing:Enable
  355. The "TaggedQueuing:Enable" or "TQ:Enable" option enables Tagged Queuing for
  356. all Target Devices on this Host Adapter, overriding any limitation that
  357. would otherwise be imposed based on the Host Adapter firmware version.
  358. TaggedQueuing:Disable
  359. The "TaggedQueuing:Disable" or "TQ:Disable" option disables Tagged Queuing
  360. for all Target Devices on this Host Adapter.
  361. TaggedQueuing:<Target-Spec>
  362. The "TaggedQueuing:<Target-Spec>" or "TQ:<Target-Spec>" option controls
  363. Tagged Queuing individually for each Target Device. <Target-Spec> is a
  364. sequence of "Y", "N", and "X" characters. "Y" enables Tagged Queuing, "N"
  365. disables Tagged Queuing, and "X" accepts the default based on the firmware
  366. version. The first character refers to Target Device 0, the second to
  367. Target Device 1, and so on; if the sequence of "Y", "N", and "X" characters
  368. does not cover all the Target Devices, unspecified characters are assumed
  369. to be "X".
  370. The BusLogic Driver Miscellaneous Options comprise the following:
  371. BusSettleTime:<seconds>
  372. The "BusSettleTime:" or "BST:" option specifies the Bus Settle Time in
  373. seconds. The Bus Settle Time is the amount of time to wait between a Host
  374. Adapter Hard Reset which initiates a SCSI Bus Reset and issuing any SCSI
  375. Commands. If unspecified, it defaults to BusLogic_DefaultBusSettleTime.
  376. InhibitTargetInquiry
  377. The "InhibitTargetInquiry" option inhibits the execution of an Inquire
  378. Target Devices or Inquire Installed Devices command on MultiMaster Host
  379. Adapters. This may be necessary with some older Target Devices that do not
  380. respond correctly when Logical Units above 0 are addressed.
  381. The BusLogic Driver Debugging Options comprise the following:
  382. TraceProbe
  383. The "TraceProbe" option enables tracing of Host Adapter Probing.
  384. TraceHardwareReset
  385. The "TraceHardwareReset" option enables tracing of Host Adapter Hardware
  386. Reset.
  387. TraceConfiguration
  388. The "TraceConfiguration" option enables tracing of Host Adapter
  389. Configuration.
  390. TraceErrors
  391. The "TraceErrors" option enables tracing of SCSI Commands that return an
  392. error from the Target Device. The CDB and Sense Data will be printed for
  393. each SCSI Command that fails.
  394. Debug
  395. The "Debug" option enables all debugging options.
  396. The following examples demonstrate setting the Queue Depth for Target Devices
  397. 1 and 2 on the first host adapter to 7 and 15, the Queue Depth for all Target
  398. Devices on the second host adapter to 31, and the Bus Settle Time on the
  399. second host adapter to 30 seconds.
  400. Linux Kernel Command Line:
  401. linux BusLogic=QueueDepth:[,7,15];QueueDepth:31,BusSettleTime:30
  402. LILO Linux Boot Loader (in /etc/lilo.conf):
  403. append = "BusLogic=QueueDepth:[,7,15];QueueDepth:31,BusSettleTime:30"
  404. INSMOD Loadable Kernel Module Installation Facility:
  405. insmod BusLogic.o \
  406. 'BusLogic="QueueDepth:[,7,15];QueueDepth:31,BusSettleTime:30"'
  407. NOTE: Module Utilities 2.1.71 or later is required for correct parsing
  408. of driver options containing commas.
  409. DRIVER INSTALLATION
  410. This distribution was prepared for Linux kernel version 2.0.35, but should be
  411. compatible with 2.0.4 or any later 2.0 series kernel.
  412. To install the new BusLogic SCSI driver, you may use the following commands,
  413. replacing "/usr/src" with wherever you keep your Linux kernel source tree:
  414. cd /usr/src
  415. tar -xvzf BusLogic-2.0.15.tar.gz
  416. mv README.* LICENSE.* BusLogic.[ch] FlashPoint.c linux/drivers/scsi
  417. patch -p0 < BusLogic.patch (only for 2.0.33 and below)
  418. cd linux
  419. make config
  420. make zImage
  421. Then install "arch/i386/boot/zImage" as your standard kernel, run lilo if
  422. appropriate, and reboot.
  423. BUSLOGIC ANNOUNCEMENTS MAILING LIST
  424. The BusLogic Announcements Mailing List provides a forum for informing Linux
  425. users of new driver releases and other announcements regarding Linux support
  426. for BusLogic SCSI Host Adapters. To join the mailing list, send a message to
  427. "buslogic-announce-request@dandelion.com" with the line "subscribe" in the
  428. message body.