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