Ysphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget!/translations/zh_CN/scsi/BusLogicmodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget!/translations/zh_TW/scsi/BusLogicmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget!/translations/it_IT/scsi/BusLogicmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget!/translations/ja_JP/scsi/BusLogicmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget!/translations/ko_KR/scsi/BusLogicmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hPortuguese (Brazilian)}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget!/translations/pt_BR/scsi/BusLogicmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget!/translations/sp_SP/scsi/BusLogicmodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhcomment)}(h SPDX-License-Identifier: GPL-2.0h]h SPDX-License-Identifier: GPL-2.0}hhsbah}(h]h ]h"]h$]h&] xml:spacepreserveuh1hhhhhh;/var/lib/git/docbuild/linux/Documentation/scsi/BusLogic.rsthKubhsection)}(hhh](htitle)}(h9BusLogic MultiMaster and FlashPoint SCSI Driver for Linuxh]h9BusLogic MultiMaster and FlashPoint SCSI Driver for Linux}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh block_quote)}(hXg Version 2.0.15 for Linux 2.0 Version 2.1.15 for Linux 2.1 PRODUCTION RELEASE 17 August 1998 Leonard N. Zubkoff Dandelion Digital lnz@dandelion.com Copyright 1995-1998 by Leonard N. Zubkoff h](h)}(hVersion 2.0.15 for Linux 2.0 Version 2.1.15 for Linux 2.1 PRODUCTION RELEASE 17 August 1998 Leonard N. Zubkoff Dandelion Digital lnz@dandelion.com h](h paragraph)}(hVersion 2.0.15 for Linux 2.0h]hVersion 2.0.15 for Linux 2.0}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhubh)}(hVersion 2.1.15 for Linux 2.1h]hVersion 2.1.15 for Linux 2.1}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hhubh)}(hbPRODUCTION RELEASE 17 August 1998 Leonard N. Zubkoff Dandelion Digital lnz@dandelion.com h](h)}(hPRODUCTION RELEASEh]hPRODUCTION RELEASE}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hjubh)}(hJ 17 August 1998 Leonard N. Zubkoff Dandelion Digital lnz@dandelion.com h](h)}(h17 August 1998 h]h)}(h17 August 1998h]h17 August 1998}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hjubah}(h]h ]h"]h$]h&]uh1hhhhK hjubh)}(hLeonard N. Zubkoffh]hLeonard N. Zubkoff}(hj3hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubh)}(hDandelion Digitalh]hDandelion Digital}(hjAhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubh)}(hlnz@dandelion.comh]h reference)}(hjQh]hlnz@dandelion.com}(hjUhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:lnz@dandelion.comuh1jShjOubah}(h]h ]h"]h$]h&]uh1hhhhKhjubeh}(h]h ]h"]h$]h&]uh1hhhhK hjubeh}(h]h ]h"]h$]h&]uh1hhhhK hhubeh}(h]h ]h"]h$]h&]uh1hhhhKhhubh)}(h=Copyright 1995-1998 by Leonard N. Zubkoff h](h+Copyright 1995-1998 by Leonard N. Zubkoff <}(hj|hhhNhNubjT)}(hlnz@dandelion.comh]hlnz@dandelion.com}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:lnz@dandelion.comuh1jShj|ubh>}(hj|hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhhubeh}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh)}(hhh](h)}(h Introductionh]h Introduction}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hXBusLogic, Inc. designed and manufactured a variety of high performance SCSI host adapters which share a common programming interface across a diverse collection of bus architectures by virtue of their MultiMaster ASIC technology. BusLogic was acquired by Mylex Corporation in February 1996, but the products supported by this driver originated under the BusLogic name and so that name is retained in the source code and documentation.h]hXBusLogic, Inc. designed and manufactured a variety of high performance SCSI host adapters which share a common programming interface across a diverse collection of bus architectures by virtue of their MultiMaster ASIC technology. BusLogic was acquired by Mylex Corporation in February 1996, but the products supported by this driver originated under the BusLogic name and so that name is retained in the source code and documentation.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hXfThis driver supports all present BusLogic MultiMaster Host Adapters, and should support any future MultiMaster designs with little or no modification. More recently, BusLogic introduced the FlashPoint Host Adapters, which are less costly and rely on the host CPU, rather than including an onboard processor. Despite not having an onboard CPU, the FlashPoint Host Adapters perform very well and have very low command latency. BusLogic has recently provided me with the FlashPoint Driver Developer's Kit, which comprises documentation and freely redistributable source code for the FlashPoint SCCB Manager. The SCCB Manager is the library of code that runs on the host CPU and performs functions analogous to the firmware on the MultiMaster Host Adapters. Thanks to their having provided the SCCB Manager, this driver now supports the FlashPoint Host Adapters as well.h]hXhThis driver supports all present BusLogic MultiMaster Host Adapters, and should support any future MultiMaster designs with little or no modification. More recently, BusLogic introduced the FlashPoint Host Adapters, which are less costly and rely on the host CPU, rather than including an onboard processor. Despite not having an onboard CPU, the FlashPoint Host Adapters perform very well and have very low command latency. BusLogic has recently provided me with the FlashPoint Driver Developer’s Kit, which comprises documentation and freely redistributable source code for the FlashPoint SCCB Manager. The SCCB Manager is the library of code that runs on the host CPU and performs functions analogous to the firmware on the MultiMaster Host Adapters. Thanks to their having provided the SCCB Manager, this driver now supports the FlashPoint Host Adapters as well.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK"hjhhubh)}(hXMy primary goals in writing this completely new BusLogic driver for Linux are to achieve the full performance that BusLogic SCSI Host Adapters and modern SCSI peripherals are capable of, and to provide a highly robust driver that can be depended upon for high performance mission critical applications. All of the major performance features can be configured from the Linux kernel command line or at module initialization time, allowing individual installations to tune driver performance and error recovery to their particular needs.h]hXMy primary goals in writing this completely new BusLogic driver for Linux are to achieve the full performance that BusLogic SCSI Host Adapters and modern SCSI peripherals are capable of, and to provide a highly robust driver that can be depended upon for high performance mission critical applications. All of the major performance features can be configured from the Linux kernel command line or at module initialization time, allowing individual installations to tune driver performance and error recovery to their particular needs.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK/hjhhubh)}(hXThe latest information on Linux support for BusLogic SCSI Host Adapters, as well as the most recent release of this driver and the latest firmware for the BT-948/958/958D, will always be available from my Linux Home Page at URL "http://sourceforge.net/projects/dandelion/".h](hThe latest information on Linux support for BusLogic SCSI Host Adapters, as well as the most recent release of this driver and the latest firmware for the BT-948/958/958D, will always be available from my Linux Home Page at URL “}(hjhhhNhNubjT)}(h*http://sourceforge.net/projects/dandelion/h]h*http://sourceforge.net/projects/dandelion/}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurijuh1jShjubh”.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK7hjhhubh)}(hXOBug reports should be sent via electronic mail to "lnz@dandelion.com". Please include with the bug report the complete configuration messages reported by the driver and SCSI subsystem at startup, along with any subsequent system messages relevant to SCSI operations, and a detailed description of your system's hardware configuration.h](h5Bug reports should be sent via electronic mail to “}(hjhhhNhNubjT)}(hlnz@dandelion.comh]hlnz@dandelion.com}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:lnz@dandelion.comuh1jShjubhX”. Please include with the bug report the complete configuration messages reported by the driver and SCSI subsystem at startup, along with any subsequent system messages relevant to SCSI operations, and a detailed description of your system’s hardware configuration.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKShjhhubh)}(hXMylex Corporation is located at 34551 Ardenwood Blvd., Fremont, California 94555, USA and can be reached at 510/796-6100 or on the World Wide Web at http://www.mylex.com. Mylex HBA Technical Support can be reached by electronic mail at techsup@mylex.com, by Voice at 510/608-2400, or by FAX at 510/745-7715. Contact information for offices in Europe and Japan is available on the Web site.h](hMylex Corporation is located at 34551 Ardenwood Blvd., Fremont, California 94555, USA and can be reached at 510/796-6100 or on the World Wide Web at }(hjLhhhNhNubjT)}(hhttp://www.mylex.comh]hhttp://www.mylex.com}(hjThhhNhNubah}(h]h ]h"]h$]h&]refurijVuh1jShjLubhD. Mylex HBA Technical Support can be reached by electronic mail at }(hjLhhhNhNubjT)}(htechsup@mylex.comh]htechsup@mylex.com}(hjghhhNhNubah}(h]h ]h"]h$]h&]refurimailto:techsup@mylex.comuh1jShjLubh, by Voice at 510/608-2400, or by FAX at 510/745-7715. Contact information for offices in Europe and Japan is available on the Web site.}(hjLhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKYhjhhubeh}(h] introductionah ]h"] introductionah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hDriver Featuresh]hDriver Features}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKbubh)}(hhh](h)}(h#Configuration Reporting and Testingh]h#Configuration Reporting and Testing}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKeubh)}(hXDuring system initialization, the driver reports extensively on the host adapter hardware configuration, including the synchronous transfer parameters requested and negotiated with each target device. AutoSCSI settings for Synchronous Negotiation, Wide Negotiation, and Disconnect/Reconnect are reported for each target device, as well as the status of Tagged Queuing. If the same setting is in effect for all target devices, then a single word or phrase is used; otherwise, a letter is provided for each target device to indicate the individual status. The following examples should clarify this reporting format: Synchronous Negotiation: Ultra Synchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 20.0 mega-transfers/second. Synchronous Negotiation: Fast Synchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 10.0 mega-transfers/second. Synchronous Negotiation: Slow Synchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 5.0 mega-transfers/second. Synchronous Negotiation: Disabled Synchronous negotiation is disabled and all target devices are limited to asynchronous operation. Synchronous Negotiation: UFSNUUU#UUUUUUUU Synchronous negotiation to Ultra speed is enabled for target devices 0 and 4 through 15, to Fast speed for target device 1, to Slow speed for target device 2, and is not permitted to target device 3. The host adapter's SCSI ID is represented by the "#". The status of Wide Negotiation, Disconnect/Reconnect, and Tagged Queuing are reported as "Enabled", Disabled", or a sequence of "Y" and "N" letters. h](h)}(hXhDuring system initialization, the driver reports extensively on the host adapter hardware configuration, including the synchronous transfer parameters requested and negotiated with each target device. AutoSCSI settings for Synchronous Negotiation, Wide Negotiation, and Disconnect/Reconnect are reported for each target device, as well as the status of Tagged Queuing. If the same setting is in effect for all target devices, then a single word or phrase is used; otherwise, a letter is provided for each target device to indicate the individual status. The following examples should clarify this reporting format:h]hXhDuring system initialization, the driver reports extensively on the host adapter hardware configuration, including the synchronous transfer parameters requested and negotiated with each target device. AutoSCSI settings for Synchronous Negotiation, Wide Negotiation, and Disconnect/Reconnect are reported for each target device, as well as the status of Tagged Queuing. If the same setting is in effect for all target devices, then a single word or phrase is used; otherwise, a letter is provided for each target device to indicate the individual status. The following examples should clarify this reporting format:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKghjubh)}(hXYSynchronous Negotiation: Ultra Synchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 20.0 mega-transfers/second. Synchronous Negotiation: Fast Synchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 10.0 mega-transfers/second. Synchronous Negotiation: Slow Synchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 5.0 mega-transfers/second. Synchronous Negotiation: Disabled Synchronous negotiation is disabled and all target devices are limited to asynchronous operation. Synchronous Negotiation: UFSNUUU#UUUUUUUU Synchronous negotiation to Ultra speed is enabled for target devices 0 and 4 through 15, to Fast speed for target device 1, to Slow speed for target device 2, and is not permitted to target device 3. The host adapter's SCSI ID is represented by the "#". The status of Wide Negotiation, Disconnect/Reconnect, and Tagged Queuing are reported as "Enabled", Disabled", or a sequence of "Y" and "N" letters. h](h)}(hSynchronous Negotiation: Ultrah]hSynchronous Negotiation: Ultra}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKqhjubh)}(hSynchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 20.0 mega-transfers/second. h]h)}(hSynchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 20.0 mega-transfers/second.h]hSynchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 20.0 mega-transfers/second.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKshjubah}(h]h ]h"]h$]h&]uh1hhhhKshjubh)}(hSynchronous Negotiation: Fasth]hSynchronous Negotiation: Fast}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKvhjubh)}(hSynchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 10.0 mega-transfers/second. h]h)}(hSynchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 10.0 mega-transfers/second.h]hSynchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 10.0 mega-transfers/second.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKxhjubah}(h]h ]h"]h$]h&]uh1hhhhKxhjubh)}(hSynchronous Negotiation: Slowh]hSynchronous Negotiation: Slow}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK{hjubh)}(hSynchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 5.0 mega-transfers/second. h]h)}(hSynchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 5.0 mega-transfers/second.h]hSynchronous negotiation is enabled for all target devices and the host adapter will attempt to negotiate for 5.0 mega-transfers/second.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK}hjubah}(h]h ]h"]h$]h&]uh1hhhhK}hjubh)}(h!Synchronous Negotiation: Disabledh]h!Synchronous Negotiation: Disabled}(hj3hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubh)}(hbSynchronous negotiation is disabled and all target devices are limited to asynchronous operation. h]h)}(haSynchronous negotiation is disabled and all target devices are limited to asynchronous operation.h]haSynchronous negotiation is disabled and all target devices are limited to asynchronous operation.}(hjEhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjAubah}(h]h ]h"]h$]h&]uh1hhhhKhjubh)}(h)Synchronous Negotiation: UFSNUUU#UUUUUUUUh]h)Synchronous Negotiation: UFSNUUU#UUUUUUUU}(hjYhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubh)}(hSynchronous negotiation to Ultra speed is enabled for target devices 0 and 4 through 15, to Fast speed for target device 1, to Slow speed for target device 2, and is not permitted to target device 3. The host adapter's SCSI ID is represented by the "#". h]h)}(hSynchronous negotiation to Ultra speed is enabled for target devices 0 and 4 through 15, to Fast speed for target device 1, to Slow speed for target device 2, and is not permitted to target device 3. The host adapter's SCSI ID is represented by the "#".h]hXSynchronous negotiation to Ultra speed is enabled for target devices 0 and 4 through 15, to Fast speed for target device 1, to Slow speed for target device 2, and is not permitted to target device 3. The host adapter’s SCSI ID is represented by the “#”.}(hjkhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjgubah}(h]h ]h"]h$]h&]uh1hhhhKhjubh)}(hThe status of Wide Negotiation, Disconnect/Reconnect, and Tagged Queuing are reported as "Enabled", Disabled", or a sequence of "Y" and "N" letters.h]hThe status of Wide Negotiation, Disconnect/Reconnect, and Tagged Queuing are reported as “Enabled”, Disabled”, or a sequence of “Y” and “N” letters.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubeh}(h]h ]h"]h$]h&]uh1hhhhKqhjubeh}(h]h ]h"]h$]h&]uh1hhhhKghjhhubeh}(h]#configuration-reporting-and-testingah ]h"]#configuration reporting and testingah$]h&]uh1hhjhhhhhKeubh)}(hhh](h)}(hPerformance Featuresh]hPerformance Features}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hX BusLogic SCSI Host Adapters directly implement SCSI-2 Tagged Queuing, and so support has been included in the driver to utilize tagged queuing with any target devices that report having the tagged queuing capability. Tagged queuing allows for multiple outstanding commands to be issued to each target device or logical unit, and can improve I/O performance substantially. In addition, BusLogic's Strict Round Robin Mode is used to optimize host adapter performance, and scatter/gather I/O can support as many segments as can be effectively utilized by the Linux I/O subsystem. Control over the use of tagged queuing for each target device as well as individual selection of the tagged queue depth is available through driver options provided on the kernel command line or at module initialization time. By default, the queue depth is determined automatically based on the host adapter's total queue depth and the number, type, speed, and capabilities of the target devices found. In addition, tagged queuing is automatically disabled whenever the host adapter firmware version is known not to implement it correctly, or whenever a tagged queue depth of 1 is selected. Tagged queuing is also disabled for individual target devices if disconnect/reconnect is disabled for that device. h]h)}(hXBusLogic SCSI Host Adapters directly implement SCSI-2 Tagged Queuing, and so support has been included in the driver to utilize tagged queuing with any target devices that report having the tagged queuing capability. Tagged queuing allows for multiple outstanding commands to be issued to each target device or logical unit, and can improve I/O performance substantially. In addition, BusLogic's Strict Round Robin Mode is used to optimize host adapter performance, and scatter/gather I/O can support as many segments as can be effectively utilized by the Linux I/O subsystem. Control over the use of tagged queuing for each target device as well as individual selection of the tagged queue depth is available through driver options provided on the kernel command line or at module initialization time. By default, the queue depth is determined automatically based on the host adapter's total queue depth and the number, type, speed, and capabilities of the target devices found. In addition, tagged queuing is automatically disabled whenever the host adapter firmware version is known not to implement it correctly, or whenever a tagged queue depth of 1 is selected. Tagged queuing is also disabled for individual target devices if disconnect/reconnect is disabled for that device.h]hX BusLogic SCSI Host Adapters directly implement SCSI-2 Tagged Queuing, and so support has been included in the driver to utilize tagged queuing with any target devices that report having the tagged queuing capability. Tagged queuing allows for multiple outstanding commands to be issued to each target device or logical unit, and can improve I/O performance substantially. In addition, BusLogic’s Strict Round Robin Mode is used to optimize host adapter performance, and scatter/gather I/O can support as many segments as can be effectively utilized by the Linux I/O subsystem. Control over the use of tagged queuing for each target device as well as individual selection of the tagged queue depth is available through driver options provided on the kernel command line or at module initialization time. By default, the queue depth is determined automatically based on the host adapter’s total queue depth and the number, type, speed, and capabilities of the target devices found. In addition, tagged queuing is automatically disabled whenever the host adapter firmware version is known not to implement it correctly, or whenever a tagged queue depth of 1 is selected. Tagged queuing is also disabled for individual target devices if disconnect/reconnect is disabled for that device.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubeh}(h]performance-featuresah ]h"]performance featuresah$]h&]uh1hhjhhhhhKubh)}(hhh](h)}(hRobustness Featuresh]hRobustness Features}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hXThe driver implements extensive error recovery procedures. When the higher level parts of the SCSI subsystem request that a timed out command be reset, a selection is made between a full host adapter hard reset and SCSI bus reset versus sending a bus device reset message to the individual target device based on the recommendation of the SCSI subsystem. Error recovery strategies are selectable through driver options individually for each target device, and also include sending a bus device reset to the specific target device associated with the command being reset, as well as suppressing error recovery entirely to avoid perturbing an improperly functioning device. If the bus device reset error recovery strategy is selected and sending a bus device reset does not restore correct operation, the next command that is reset will force a full host adapter hard reset and SCSI bus reset. SCSI bus resets caused by other devices and detected by the host adapter are also handled by issuing a soft reset to the host adapter and re-initialization. Finally, if tagged queuing is active and more than one command reset occurs in a 10 minute interval, or if a command reset occurs within the first 10 minutes of operation, then tagged queuing will be disabled for that target device. These error recovery options improve overall system robustness by preventing individual errant devices from causing the system as a whole to lock up or crash, and thereby allowing a clean shutdown and restart after the offending component is removed. h]h)}(hXThe driver implements extensive error recovery procedures. When the higher level parts of the SCSI subsystem request that a timed out command be reset, a selection is made between a full host adapter hard reset and SCSI bus reset versus sending a bus device reset message to the individual target device based on the recommendation of the SCSI subsystem. Error recovery strategies are selectable through driver options individually for each target device, and also include sending a bus device reset to the specific target device associated with the command being reset, as well as suppressing error recovery entirely to avoid perturbing an improperly functioning device. If the bus device reset error recovery strategy is selected and sending a bus device reset does not restore correct operation, the next command that is reset will force a full host adapter hard reset and SCSI bus reset. SCSI bus resets caused by other devices and detected by the host adapter are also handled by issuing a soft reset to the host adapter and re-initialization. Finally, if tagged queuing is active and more than one command reset occurs in a 10 minute interval, or if a command reset occurs within the first 10 minutes of operation, then tagged queuing will be disabled for that target device. These error recovery options improve overall system robustness by preventing individual errant devices from causing the system as a whole to lock up or crash, and thereby allowing a clean shutdown and restart after the offending component is removed.h]hXThe driver implements extensive error recovery procedures. When the higher level parts of the SCSI subsystem request that a timed out command be reset, a selection is made between a full host adapter hard reset and SCSI bus reset versus sending a bus device reset message to the individual target device based on the recommendation of the SCSI subsystem. Error recovery strategies are selectable through driver options individually for each target device, and also include sending a bus device reset to the specific target device associated with the command being reset, as well as suppressing error recovery entirely to avoid perturbing an improperly functioning device. If the bus device reset error recovery strategy is selected and sending a bus device reset does not restore correct operation, the next command that is reset will force a full host adapter hard reset and SCSI bus reset. SCSI bus resets caused by other devices and detected by the host adapter are also handled by issuing a soft reset to the host adapter and re-initialization. Finally, if tagged queuing is active and more than one command reset occurs in a 10 minute interval, or if a command reset occurs within the first 10 minutes of operation, then tagged queuing will be disabled for that target device. These error recovery options improve overall system robustness by preventing individual errant devices from causing the system as a whole to lock up or crash, and thereby allowing a clean shutdown and restart after the offending component is removed.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubeh}(h]robustness-featuresah ]h"]robustness featuresah$]h&]uh1hhjhhhhhKubh)}(hhh](h)}(hPCI Configuration Supporth]hPCI Configuration Support}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hXOn PCI systems running kernels compiled with PCI BIOS support enabled, this driver will interrogate the PCI configuration space and use the I/O port addresses assigned by the system BIOS, rather than the ISA compatible I/O port addresses. The ISA compatible I/O port address is then disabled by the driver. On PCI systems it is also recommended that the AutoSCSI utility be used to disable the ISA compatible I/O port entirely as it is not necessary. The ISA compatible I/O port is disabled by default on the BT-948/958/958D. h]h)}(hXOn PCI systems running kernels compiled with PCI BIOS support enabled, this driver will interrogate the PCI configuration space and use the I/O port addresses assigned by the system BIOS, rather than the ISA compatible I/O port addresses. The ISA compatible I/O port address is then disabled by the driver. On PCI systems it is also recommended that the AutoSCSI utility be used to disable the ISA compatible I/O port entirely as it is not necessary. The ISA compatible I/O port is disabled by default on the BT-948/958/958D.h]hXOn PCI systems running kernels compiled with PCI BIOS support enabled, this driver will interrogate the PCI configuration space and use the I/O port addresses assigned by the system BIOS, rather than the ISA compatible I/O port addresses. The ISA compatible I/O port address is then disabled by the driver. On PCI systems it is also recommended that the AutoSCSI utility be used to disable the ISA compatible I/O port entirely as it is not necessary. The ISA compatible I/O port is disabled by default on the BT-948/958/958D.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubeh}(h]pci-configuration-supportah ]h"]pci configuration supportah$]h&]uh1hhjhhhhhKubh)}(hhh](h)}(h/proc File System Supporth]h/proc File System Support}(hj7hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj4hhhhhKubh)}(hCopies of the host adapter configuration information together with updated data transfer and error recovery statistics are available through the /proc/scsi/BusLogic/ interface. h]h)}(hCopies of the host adapter configuration information together with updated data transfer and error recovery statistics are available through the /proc/scsi/BusLogic/ interface.h]hCopies of the host adapter configuration information together with updated data transfer and error recovery statistics are available through the /proc/scsi/BusLogic/ interface.}(hjIhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjEubah}(h]h ]h"]h$]h&]uh1hhhhKhj4hhubeh}(h]proc-file-system-supportah ]h"]/proc file system supportah$]h&]uh1hhjhhhhhKubh)}(hhh](h)}(hShared Interrupts Supporth]hShared Interrupts Support}(hjhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjehhhhhKubh)}(hOn systems that support shared interrupts, any number of BusLogic Host Adapters may share the same interrupt request channel. h]h)}(h}On systems that support shared interrupts, any number of BusLogic Host Adapters may share the same interrupt request channel.h]h}On systems that support shared interrupts, any number of BusLogic Host Adapters may share the same interrupt request channel.}(hjzhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjvubah}(h]h ]h"]h$]h&]uh1hhhhKhjehhubeh}(h]shared-interrupts-supportah ]h"]shared interrupts supportah$]h&]uh1hhjhhhhhKubeh}(h]driver-featuresah ]h"]driver featuresah$]h&]uh1hhhhhhhhKbubh)}(hhh](h)}(hSupported Host Adaptersh]hSupported Host Adapters}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hX The following list comprises the supported BusLogic SCSI Host Adapters as of the date of this document. It is recommended that anyone purchasing a BusLogic Host Adapter not in the following table contact the author beforehand to verify that it is or will be supported.h]hX The following list comprises the supported BusLogic SCSI Host Adapters as of the date of this document. It is recommended that anyone purchasing a BusLogic Host Adapter not in the following table contact the author beforehand to verify that it is or will be supported.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(h$FlashPoint Series PCI Host Adapters:h]h$FlashPoint Series PCI Host Adapters:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubhtable)}(hhh]htgroup)}(hhh](hcolspec)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhjubj)}(hhh]h}(h]h ]h"]h$]h&]colwidthK-uh1jhjubhtbody)}(hhh](hrow)}(hhh](hentry)}(hhh]h)}(hFlashPoint LT (BT-930)h]hFlashPoint LT (BT-930)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h Ultra SCSI-3h]h Ultra SCSI-3}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hFlashPoint LT (BT-930R)h]hFlashPoint LT (BT-930R)}(hj1hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj.ubah}(h]h ]h"]h$]h&]uh1jhj+ubj)}(hhh]h)}(hUltra SCSI-3 with RAIDPlush]hUltra SCSI-3 with RAIDPlus}(hjHhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjEubah}(h]h ]h"]h$]h&]uh1jhj+ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hFlashPoint LT (BT-920)h]hFlashPoint LT (BT-920)}(hjhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjeubah}(h]h ]h"]h$]h&]uh1jhjbubj)}(hhh]h)}(h"Ultra SCSI-3 (BT-930 without BIOS)h]h"Ultra SCSI-3 (BT-930 without BIOS)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj|ubah}(h]h ]h"]h$]h&]uh1jhjbubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hFlashPoint DL (BT-932)h]hFlashPoint DL (BT-932)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hDual Channel Ultra SCSI-3h]hDual Channel Ultra SCSI-3}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hFlashPoint DL (BT-932R)h]hFlashPoint DL (BT-932R)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h'Dual Channel Ultra SCSI-3 with RAIDPlush]h'Dual Channel Ultra SCSI-3 with RAIDPlus}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hFlashPoint LW (BT-950)h]hFlashPoint LW (BT-950)}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hWide Ultra SCSI-3h]hWide Ultra SCSI-3}(hj$hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj!ubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hFlashPoint LW (BT-950R)h]hFlashPoint LW (BT-950R)}(hjDhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjAubah}(h]h ]h"]h$]h&]uh1jhj>ubj)}(hhh]h)}(hWide Ultra SCSI-3 with RAIDPlush]hWide Ultra SCSI-3 with RAIDPlus}(hj[hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjXubah}(h]h ]h"]h$]h&]uh1jhj>ubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hFlashPoint DW (BT-952)h]hFlashPoint DW (BT-952)}(hj{hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjxubah}(h]h ]h"]h$]h&]uh1jhjuubj)}(hhh]h)}(hDual Channel Wide Ultra SCSI-3h]hDual Channel Wide Ultra SCSI-3}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjuubeh}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh](j)}(hhh]h)}(hFlashPoint DW (BT-952R)h]hFlashPoint DW (BT-952R)}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(h,Dual Channel Wide Ultra SCSI-3 with RAIDPlush]h,Dual Channel Wide Ultra SCSI-3 with RAIDPlus}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]colsKuh1jhjubah}(h]h ]h"]h$]h&]uh1jhjhhhhhNubh)}(h%MultiMaster "W" Series Host Adapters:h]h)MultiMaster “W” Series Host Adapters:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubj)}(hhh]j)}(hhh](j)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhjubj)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhjubj)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhjubj)}(hhh](j)}(hhh](j)}(hhh]h)}(hBT-948h]hBT-948}(hj1hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj.ubah}(h]h ]h"]h$]h&]uh1jhj+ubj)}(hhh]h)}(hPCIh]hPCI}(hjHhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjEubah}(h]h ]h"]h$]h&]uh1jhj+ubj)}(hhh]h)}(h Ultra SCSI-3h]h Ultra SCSI-3}(hj_hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj\ubah}(h]h ]h"]h$]h&]uh1jhj+ubeh}(h]h ]h"]h$]h&]uh1jhj(ubj)}(hhh](j)}(hhh]h)}(hBT-958h]hBT-958}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj|ubah}(h]h ]h"]h$]h&]uh1jhjyubj)}(hhh]h)}(hPCIh]hPCI}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjyubj)}(hhh]h)}(hWide Ultra SCSI-3h]hWide Ultra SCSI-3}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjyubeh}(h]h ]h"]h$]h&]uh1jhj(ubj)}(hhh](j)}(hhh]h)}(hBT-958Dh]hBT-958D}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hPCIh]hPCI}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hWide Differential Ultra SCSI-3h]hWide Differential Ultra SCSI-3}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhj(ubeh}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]colsKuh1jhjubah}(h]h ]h"]h$]h&]uh1jhjhhhhhNubh)}(h%MultiMaster "C" Series Host Adapters:h]h)MultiMaster “C” Series Host Adapters:}(hj(hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubj)}(hhh]j)}(hhh](j)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhj9ubj)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhj9ubj)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhj9ubj)}(hhh](j)}(hhh](j)}(hhh]h)}(hBT-946Ch]hBT-946C}(hjchhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj`ubah}(h]h ]h"]h$]h&]uh1jhj]ubj)}(hhh]h)}(hPCIh]hPCI}(hjzhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjwubah}(h]h ]h"]h$]h&]uh1jhj]ubj)}(hhh]h)}(h Fast SCSI-2h]h Fast SCSI-2}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhj]ubeh}(h]h ]h"]h$]h&]uh1jhjZubj)}(hhh](j)}(hhh]h)}(hBT-956Ch]hBT-956C}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hPCIh]hPCI}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hWide Fast SCSI-2h]hWide Fast SCSI-2}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjZubj)}(hhh](j)}(hhh]h)}(hBT-956CDh]hBT-956CD}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hPCIh]hPCI}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1jhjubj)}(hhh]h)}(hWide Differential Fast SCSI-2h]hWide Differential Fast SCSI-2}(hj- hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj* ubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1jhjZubj)}(hhh](j)}(hhh]h)}(hBT-445Ch]hBT-445C}(hjM hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjJ ubah}(h]h ]h"]h$]h&]uh1jhjG ubj)}(hhh]h)}(hVLBh]hVLB}(hjd hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhja ubah}(h]h ]h"]h$]h&]uh1jhjG ubj)}(hhh]h)}(h Fast SCSI-2h]h Fast SCSI-2}(hj{ hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjx ubah}(h]h ]h"]h$]h&]uh1jhjG ubeh}(h]h ]h"]h$]h&]uh1jhjZubj)}(hhh](j)}(hhh]h)}(hBT-747Ch]hBT-747C}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(hEISAh]hEISA}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(h Fast SCSI-2h]h Fast SCSI-2}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhjZubj)}(hhh](j)}(hhh]h)}(hBT-757Ch]hBT-757C}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(hEISAh]hEISA}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(hWide Fast SCSI-2h]hWide Fast SCSI-2}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhjZubj)}(hhh](j)}(hhh]h)}(hBT-757CDh]hBT-757CD}(hj7 hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj4 ubah}(h]h ]h"]h$]h&]uh1jhj1 ubj)}(hhh]h)}(hEISAh]hEISA}(hjN hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjK ubah}(h]h ]h"]h$]h&]uh1jhj1 ubj)}(hhh]h)}(hWide Differential Fast SCSI-2h]hWide Differential Fast SCSI-2}(hje hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjb ubah}(h]h ]h"]h$]h&]uh1jhj1 ubeh}(h]h ]h"]h$]h&]uh1jhjZubeh}(h]h ]h"]h$]h&]uh1jhj9ubeh}(h]h ]h"]h$]h&]colsKuh1jhj6ubah}(h]h ]h"]h$]h&]uh1jhjhhhhhNubh)}(h%MultiMaster "S" Series Host Adapters:h]h)MultiMaster “S” Series Host Adapters:}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubj)}(hhh]j)}(hhh](j)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhj ubj)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhj ubj)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhj ubj)}(hhh](j)}(hhh](j)}(hhh]h)}(hBT-445Sh]hBT-445S}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(hVLBh]hVLB}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(h Fast SCSI-2h]h Fast SCSI-2}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh](j)}(hhh]h)}(hBT-747Sh]hBT-747S}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(hEISAh]hEISA}(hj2 hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj/ ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(h Fast SCSI-2h]h Fast SCSI-2}(hjI hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjF ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh](j)}(hhh]h)}(hBT-747Dh]hBT-747D}(hji hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjf ubah}(h]h ]h"]h$]h&]uh1jhjc ubj)}(hhh]h)}(hEISAh]hEISA}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj} ubah}(h]h ]h"]h$]h&]uh1jhjc ubj)}(hhh]h)}(hDifferential Fast SCSI-2h]hDifferential Fast SCSI-2}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhjc ubeh}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh](j)}(hhh]h)}(hBT-757Sh]hBT-757S}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(hEISAh]hEISA}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(hWide Fast SCSI-2h]hWide Fast SCSI-2}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh](j)}(hhh]h)}(hBT-757Dh]hBT-757D}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(hEISAh]hEISA}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(hWide Differential Fast SCSI-2h]hWide Differential Fast SCSI-2}(hj3 hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj0 ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh](j)}(hhh]h)}(hBT-742Ah]hBT-742A}(hjS hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjP ubah}(h]h ]h"]h$]h&]uh1jhjM ubj)}(hhh]h)}(hEISAh]hEISA}(hjj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjg ubah}(h]h ]h"]h$]h&]uh1jhjM ubj)}(hhh]h)}(hSCSI-2 (742A revision H)h]hSCSI-2 (742A revision H)}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj~ ubah}(h]h ]h"]h$]h&]uh1jhjM ubeh}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]colsKuh1jhj ubah}(h]h ]h"]h$]h&]uh1jhjhhhhhNubh)}(h%MultiMaster "A" Series Host Adapters:h]h)MultiMaster “A” Series Host Adapters:}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hjhhubj)}(hhh]j)}(hhh](j)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhj ubj)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhj ubj)}(hhh]h}(h]h ]h"]h$]h&]colwidthKuh1jhj ubj)}(hhh]j)}(hhh](j)}(hhh]h)}(hBT-742Ah]hBT-742A}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(hEISAh]hEISA}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubj)}(hhh]h)}(hSCSI-2 (742A revisions A - G)h]hSCSI-2 (742A revisions A - G)}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]uh1jhj ubah}(h]h ]h"]h$]h&]uh1jhj ubeh}(h]h ]h"]h$]h&]colsKuh1jhj ubah}(h]h ]h"]h$]h&]uh1jhjhhhhhNubh)}(hgAMI FastDisk Host Adapters that are true BusLogic MultiMaster clones are also supported by this driver.h]hgAMI FastDisk Host Adapters that are true BusLogic MultiMaster clones are also supported by this driver.}(hjD hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hXBusLogic SCSI Host Adapters are available packaged both as bare boards and as retail kits. The BT- model numbers above refer to the bare board packaging. The retail kit model numbers are found by replacing BT- with KT- in the above list. The retail kit includes the bare board and manual as well as cabling and driver media and documentation that are not provided with bare boards.h]hXBusLogic SCSI Host Adapters are available packaged both as bare boards and as retail kits. The BT- model numbers above refer to the bare board packaging. The retail kit model numbers are found by replacing BT- with KT- in the above list. The retail kit includes the bare board and manual as well as cabling and driver media and documentation that are not provided with bare boards.}(hjR hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubeh}(h]supported-host-adaptersah ]h"]supported host adaptersah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hFlashPoint Installation Notesh]hFlashPoint Installation Notes}(hjk hhhNhNubah}(h]h ]h"]h$]h&]uh1hhjh hhhhhMubh)}(hhh](h)}(hRAIDPlus Supporth]hRAIDPlus Support}(hj| hhhNhNubah}(h]h ]h"]h$]h&]uh1hhjy hhhhhMubh)}(hX!FlashPoint Host Adapters now include RAIDPlus, Mylex's bootable software RAID. RAIDPlus is not supported on Linux, and there are no plans to support it. The MD driver in Linux 2.0 provides for concatenation (LINEAR) and striping (RAID-0), and support for mirroring (RAID-1), fixed parity (RAID-4), and distributed parity (RAID-5) is available separately. The built-in Linux RAID support is generally more flexible and is expected to perform better than RAIDPlus, so there is little impetus to include RAIDPlus support in the BusLogic driver. h]h)}(hX FlashPoint Host Adapters now include RAIDPlus, Mylex's bootable software RAID. RAIDPlus is not supported on Linux, and there are no plans to support it. The MD driver in Linux 2.0 provides for concatenation (LINEAR) and striping (RAID-0), and support for mirroring (RAID-1), fixed parity (RAID-4), and distributed parity (RAID-5) is available separately. The built-in Linux RAID support is generally more flexible and is expected to perform better than RAIDPlus, so there is little impetus to include RAIDPlus support in the BusLogic driver.h]hX"FlashPoint Host Adapters now include RAIDPlus, Mylex’s bootable software RAID. RAIDPlus is not supported on Linux, and there are no plans to support it. The MD driver in Linux 2.0 provides for concatenation (LINEAR) and striping (RAID-0), and support for mirroring (RAID-1), fixed parity (RAID-4), and distributed parity (RAID-5) is available separately. The built-in Linux RAID support is generally more flexible and is expected to perform better than RAIDPlus, so there is little impetus to include RAIDPlus support in the BusLogic driver.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM!hj ubah}(h]h ]h"]h$]h&]uh1hhhhM!hjy hhubeh}(h]raidplus-supportah ]h"]raidplus supportah$]h&]uh1hhjh hhhhhMubh)}(hhh](h)}(hEnabling UltraSCSI Transfersh]hEnabling UltraSCSI Transfers}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj hhhhhM+ubh)}(hXFlashPoint Host Adapters ship with their configuration set to "Factory Default" settings that are conservative and do not allow for UltraSCSI speed to be negotiated. This results in fewer problems when these host adapters are installed in systems with cabling or termination that is not sufficient for UltraSCSI operation, or where existing SCSI devices do not properly respond to synchronous transfer negotiation for UltraSCSI speed. AutoSCSI may be used to load "Optimum Performance" settings which allow UltraSCSI speed to be negotiated with all devices, or UltraSCSI speed can be enabled on an individual basis. It is recommended that SCAM be manually disabled after the "Optimum Performance" settings are loaded. h]h)}(hXFlashPoint Host Adapters ship with their configuration set to "Factory Default" settings that are conservative and do not allow for UltraSCSI speed to be negotiated. This results in fewer problems when these host adapters are installed in systems with cabling or termination that is not sufficient for UltraSCSI operation, or where existing SCSI devices do not properly respond to synchronous transfer negotiation for UltraSCSI speed. AutoSCSI may be used to load "Optimum Performance" settings which allow UltraSCSI speed to be negotiated with all devices, or UltraSCSI speed can be enabled on an individual basis. It is recommended that SCAM be manually disabled after the "Optimum Performance" settings are loaded.h]hXFlashPoint Host Adapters ship with their configuration set to “Factory Default” settings that are conservative and do not allow for UltraSCSI speed to be negotiated. This results in fewer problems when these host adapters are installed in systems with cabling or termination that is not sufficient for UltraSCSI operation, or where existing SCSI devices do not properly respond to synchronous transfer negotiation for UltraSCSI speed. AutoSCSI may be used to load “Optimum Performance” settings which allow UltraSCSI speed to be negotiated with all devices, or UltraSCSI speed can be enabled on an individual basis. It is recommended that SCAM be manually disabled after the “Optimum Performance” settings are loaded.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM-hj ubah}(h]h ]h"]h$]h&]uh1hhhhM-hj hhubeh}(h]enabling-ultrascsi-transfersah ]h"]h$]enabling ultrascsi transfersah&]uh1hhjh hhhhhM+ referencedKubeh}(h]flashpoint-installation-notesah ]h"]flashpoint installation notesah$]h&]uh1hhhhhhhhMubh)}(hhh](h)}(h"BT-948/958/958D Installation Notesh]h"BT-948/958/958D Installation Notes}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj hhhhhM:ubh)}(hThe BT-948/958/958D PCI Ultra SCSI Host Adapters have some features which may require attention in some circumstances when installing Linux.h]hThe BT-948/958/958D PCI Ultra SCSI Host Adapters have some features which may require attention in some circumstances when installing Linux.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM<hj hhubh)}(hhh](h)}(hPCI I/O Port Assignmentsh]hPCI I/O Port Assignments}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhM@ubh)}(hX|When configured to factory default settings, the BT-948/958/958D will only recognize the PCI I/O port assignments made by the motherboard's PCI BIOS. The BT-948/958/958D will not respond to any of the ISA compatible I/O ports that previous BusLogic SCSI Host Adapters respond to. This driver supports the PCI I/O port assignments, so this is the preferred configuration. However, if the obsolete BusLogic driver must be used for any reason, such as a Linux distribution that does not yet use this driver in its boot kernel, BusLogic has provided an AutoSCSI configuration option to enable a legacy ISA compatible I/O port. To enable this backward compatibility option, invoke the AutoSCSI utility via Ctrl-B at system startup and select "Adapter Configuration", "View/Modify Configuration", and then change the "ISA Compatible Port" setting from "Disable" to "Primary" or "Alternate". Once this driver has been installed, the "ISA Compatible Port" option should be set back to "Disable" to avoid possible future I/O port conflicts. The older BT-946C/956C/956CD also have this configuration option, but the factory default setting is "Primary". h](h)}(hXoWhen configured to factory default settings, the BT-948/958/958D will only recognize the PCI I/O port assignments made by the motherboard's PCI BIOS. The BT-948/958/958D will not respond to any of the ISA compatible I/O ports that previous BusLogic SCSI Host Adapters respond to. This driver supports the PCI I/O port assignments, so this is the preferred configuration. However, if the obsolete BusLogic driver must be used for any reason, such as a Linux distribution that does not yet use this driver in its boot kernel, BusLogic has provided an AutoSCSI configuration option to enable a legacy ISA compatible I/O port.h]hXqWhen configured to factory default settings, the BT-948/958/958D will only recognize the PCI I/O port assignments made by the motherboard’s PCI BIOS. The BT-948/958/958D will not respond to any of the ISA compatible I/O ports that previous BusLogic SCSI Host Adapters respond to. This driver supports the PCI I/O port assignments, so this is the preferred configuration. However, if the obsolete BusLogic driver must be used for any reason, such as a Linux distribution that does not yet use this driver in its boot kernel, BusLogic has provided an AutoSCSI configuration option to enable a legacy ISA compatible I/O port.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMBhjubh)}(hX To enable this backward compatibility option, invoke the AutoSCSI utility via Ctrl-B at system startup and select "Adapter Configuration", "View/Modify Configuration", and then change the "ISA Compatible Port" setting from "Disable" to "Primary" or "Alternate". Once this driver has been installed, the "ISA Compatible Port" option should be set back to "Disable" to avoid possible future I/O port conflicts. The older BT-946C/956C/956CD also have this configuration option, but the factory default setting is "Primary".h]hX.To enable this backward compatibility option, invoke the AutoSCSI utility via Ctrl-B at system startup and select “Adapter Configuration”, “View/Modify Configuration”, and then change the “ISA Compatible Port” setting from “Disable” to “Primary” or “Alternate”. Once this driver has been installed, the “ISA Compatible Port” option should be set back to “Disable” to avoid possible future I/O port conflicts. The older BT-946C/956C/956CD also have this configuration option, but the factory default setting is “Primary”.}(hj&hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMLhjubeh}(h]h ]h"]h$]h&]uh1hhhhMBhjhhubeh}(h]pci-i-o-port-assignmentsah ]h"]pci i/o port assignmentsah$]h&]uh1hhj hhhhhM@ubh)}(hhh](h)}(hPCI Slot Scanning Orderh]hPCI Slot Scanning Order}(hjEhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjBhhhhhMUubh)}(hXIn systems with multiple BusLogic PCI Host Adapters, the order in which the PCI slots are scanned may appear reversed with the BT-948/958/958D as compared to the BT-946C/956C/956CD. For booting from a SCSI disk to work correctly, it is necessary that the host adapter's BIOS and the kernel agree on which disk is the boot device, which requires that they recognize the PCI host adapters in the same order. The motherboard's PCI BIOS provides a standard way of enumerating the PCI host adapters, which is used by the Linux kernel. Some PCI BIOS implementations enumerate the PCI slots in order of increasing bus number and device number, while others do so in the opposite direction. Unfortunately, Microsoft decided that Windows 95 would always enumerate the PCI slots in order of increasing bus number and device number regardless of the PCI BIOS enumeration, and requires that their scheme be supported by the host adapter's BIOS to receive Windows 95 certification. Therefore, the factory default settings of the BT-948/958/958D enumerate the host adapters by increasing bus number and device number. To disable this feature, invoke the AutoSCSI utility via Ctrl-B at system startup and select "Adapter Configuration", "View/Modify Configuration", press Ctrl-F10, and then change the "Use Bus And Device # For PCI Scanning Seq." option to OFF. This driver will interrogate the setting of the PCI Scanning Sequence option so as to recognize the host adapters in the same order as they are enumerated by the host adapter's BIOS. h](h)}(hXIn systems with multiple BusLogic PCI Host Adapters, the order in which the PCI slots are scanned may appear reversed with the BT-948/958/958D as compared to the BT-946C/956C/956CD. For booting from a SCSI disk to work correctly, it is necessary that the host adapter's BIOS and the kernel agree on which disk is the boot device, which requires that they recognize the PCI host adapters in the same order. The motherboard's PCI BIOS provides a standard way of enumerating the PCI host adapters, which is used by the Linux kernel. Some PCI BIOS implementations enumerate the PCI slots in order of increasing bus number and device number, while others do so in the opposite direction.h]hXIn systems with multiple BusLogic PCI Host Adapters, the order in which the PCI slots are scanned may appear reversed with the BT-948/958/958D as compared to the BT-946C/956C/956CD. For booting from a SCSI disk to work correctly, it is necessary that the host adapter’s BIOS and the kernel agree on which disk is the boot device, which requires that they recognize the PCI host adapters in the same order. The motherboard’s PCI BIOS provides a standard way of enumerating the PCI host adapters, which is used by the Linux kernel. Some PCI BIOS implementations enumerate the PCI slots in order of increasing bus number and device number, while others do so in the opposite direction.}(hjWhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMWhjSubh)}(hXUnfortunately, Microsoft decided that Windows 95 would always enumerate the PCI slots in order of increasing bus number and device number regardless of the PCI BIOS enumeration, and requires that their scheme be supported by the host adapter's BIOS to receive Windows 95 certification. Therefore, the factory default settings of the BT-948/958/958D enumerate the host adapters by increasing bus number and device number. To disable this feature, invoke the AutoSCSI utility via Ctrl-B at system startup and select "Adapter Configuration", "View/Modify Configuration", press Ctrl-F10, and then change the "Use Bus And Device # For PCI Scanning Seq." option to OFF.h]hXUnfortunately, Microsoft decided that Windows 95 would always enumerate the PCI slots in order of increasing bus number and device number regardless of the PCI BIOS enumeration, and requires that their scheme be supported by the host adapter’s BIOS to receive Windows 95 certification. Therefore, the factory default settings of the BT-948/958/958D enumerate the host adapters by increasing bus number and device number. To disable this feature, invoke the AutoSCSI utility via Ctrl-B at system startup and select “Adapter Configuration”, “View/Modify Configuration”, press Ctrl-F10, and then change the “Use Bus And Device # For PCI Scanning Seq.” option to OFF.}(hjehhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMbhjSubh)}(hThis driver will interrogate the setting of the PCI Scanning Sequence option so as to recognize the host adapters in the same order as they are enumerated by the host adapter's BIOS.h]hThis driver will interrogate the setting of the PCI Scanning Sequence option so as to recognize the host adapters in the same order as they are enumerated by the host adapter’s BIOS.}(hjshhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMlhjSubeh}(h]h ]h"]h$]h&]uh1hhhhMWhjBhhubeh}(h]pci-slot-scanning-orderah ]h"]pci slot scanning orderah$]h&]uh1hhj hhhhhMUubh)}(hhh](h)}(hEnabling UltraSCSI Transfersh]hEnabling UltraSCSI Transfers}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMqubh)}(hXThe BT-948/958/958D ship with their configuration set to "Factory Default" settings that are conservative and do not allow for UltraSCSI speed to be negotiated. This results in fewer problems when these host adapters are installed in systems with cabling or termination that is not sufficient for UltraSCSI operation, or where existing SCSI devices do not properly respond to synchronous transfer negotiation for UltraSCSI speed. AutoSCSI may be used to load "Optimum Performance" settings which allow UltraSCSI speed to be negotiated with all devices, or UltraSCSI speed can be enabled on an individual basis. It is recommended that SCAM be manually disabled after the "Optimum Performance" settings are loaded. h]h)}(hXThe BT-948/958/958D ship with their configuration set to "Factory Default" settings that are conservative and do not allow for UltraSCSI speed to be negotiated. This results in fewer problems when these host adapters are installed in systems with cabling or termination that is not sufficient for UltraSCSI operation, or where existing SCSI devices do not properly respond to synchronous transfer negotiation for UltraSCSI speed. AutoSCSI may be used to load "Optimum Performance" settings which allow UltraSCSI speed to be negotiated with all devices, or UltraSCSI speed can be enabled on an individual basis. It is recommended that SCAM be manually disabled after the "Optimum Performance" settings are loaded.h]hXThe BT-948/958/958D ship with their configuration set to “Factory Default” settings that are conservative and do not allow for UltraSCSI speed to be negotiated. This results in fewer problems when these host adapters are installed in systems with cabling or termination that is not sufficient for UltraSCSI operation, or where existing SCSI devices do not properly respond to synchronous transfer negotiation for UltraSCSI speed. AutoSCSI may be used to load “Optimum Performance” settings which allow UltraSCSI speed to be negotiated with all devices, or UltraSCSI speed can be enabled on an individual basis. It is recommended that SCAM be manually disabled after the “Optimum Performance” settings are loaded.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMshjubah}(h]h ]h"]h$]h&]uh1hhhhMshjhhubeh}(h]id1ah ]h"]h$]j ah&]uh1hhj hhhhhMqj Kubeh}(h]"bt-948-958-958d-installation-notesah ]h"]"bt-948/958/958d installation notesah$]h&]uh1hhhhhhhhM:ubh)}(hhh](h)}(hDriver Optionsh]hDriver Options}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhMubh)}(hX(BusLogic Driver Options may be specified either via the Linux Kernel Command Line or via the Loadable Kernel Module Installation Facility. Driver Options for multiple host adapters may be specified either by separating the option strings by a semicolon, or by specifying multiple "BusLogic=" strings on the command line. Individual option specifications for a single host adapter are separated by commas. The Probing and Debugging Options apply to all host adapters whereas the remaining options apply individually only to the selected host adapter.h]hX,BusLogic Driver Options may be specified either via the Linux Kernel Command Line or via the Loadable Kernel Module Installation Facility. Driver Options for multiple host adapters may be specified either by separating the option strings by a semicolon, or by specifying multiple “BusLogic=” strings on the command line. Individual option specifications for a single host adapter are separated by commas. The Probing and Debugging Options apply to all host adapters whereas the remaining options apply individually only to the selected host adapter.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(h;The BusLogic Driver Probing Options comprise the following:h]h;The BusLogic Driver Probing Options comprise the following:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hNoProbeh]hNoProbe}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hdThe "NoProbe" option disables all probing and therefore no BusLogic Host Adapters will be detected. h]h)}(hcThe "NoProbe" option disables all probing and therefore no BusLogic Host Adapters will be detected.h]hgThe “NoProbe” option disables all probing and therefore no BusLogic Host Adapters will be detected.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(h NoProbePCIh]h NoProbePCI}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hXThe "NoProbePCI" options disables the interrogation of PCI Configuration Space and therefore only ISA Multimaster Host Adapters will be detected, as well as PCI Multimaster Host Adapters that have their ISA Compatible I/O Port set to "Primary" or "Alternate". h]h)}(hXThe "NoProbePCI" options disables the interrogation of PCI Configuration Space and therefore only ISA Multimaster Host Adapters will be detected, as well as PCI Multimaster Host Adapters that have their ISA Compatible I/O Port set to "Primary" or "Alternate".h]hXThe “NoProbePCI” options disables the interrogation of PCI Configuration Space and therefore only ISA Multimaster Host Adapters will be detected, as well as PCI Multimaster Host Adapters that have their ISA Compatible I/O Port set to “Primary” or “Alternate”.}(hj,hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj(ubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(h NoSortPCIh]h NoSortPCI}(hj@hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hThe "NoSortPCI" option forces PCI MultiMaster Host Adapters to be enumerated in the order provided by the PCI BIOS, ignoring any setting of the AutoSCSI "Use Bus And Device # For PCI Scanning Seq." option. h]h)}(hThe "NoSortPCI" option forces PCI MultiMaster Host Adapters to be enumerated in the order provided by the PCI BIOS, ignoring any setting of the AutoSCSI "Use Bus And Device # For PCI Scanning Seq." option.h]hThe “NoSortPCI” option forces PCI MultiMaster Host Adapters to be enumerated in the order provided by the PCI BIOS, ignoring any setting of the AutoSCSI “Use Bus And Device # For PCI Scanning Seq.” option.}(hjRhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hMultiMasterFirsth]hMultiMasterFirst}(hjfhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hXThe "MultiMasterFirst" option forces MultiMaster Host Adapters to be probed before FlashPoint Host Adapters. By default, if both FlashPoint and PCI MultiMaster Host Adapters are present, this driver will probe for FlashPoint Host Adapters first unless the BIOS primary disk is controlled by the first PCI MultiMaster Host Adapter, in which case MultiMaster Host Adapters will be probed first. h]h)}(hXThe "MultiMasterFirst" option forces MultiMaster Host Adapters to be probed before FlashPoint Host Adapters. By default, if both FlashPoint and PCI MultiMaster Host Adapters are present, this driver will probe for FlashPoint Host Adapters first unless the BIOS primary disk is controlled by the first PCI MultiMaster Host Adapter, in which case MultiMaster Host Adapters will be probed first.h]hXThe “MultiMasterFirst” option forces MultiMaster Host Adapters to be probed before FlashPoint Host Adapters. By default, if both FlashPoint and PCI MultiMaster Host Adapters are present, this driver will probe for FlashPoint Host Adapters first unless the BIOS primary disk is controlled by the first PCI MultiMaster Host Adapter, in which case MultiMaster Host Adapters will be probed first.}(hjxhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjtubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hFlashPointFirsth]hFlashPointFirst}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hlThe "FlashPointFirst" option forces FlashPoint Host Adapters to be probed before MultiMaster Host Adapters. h]h)}(hkThe "FlashPointFirst" option forces FlashPoint Host Adapters to be probed before MultiMaster Host Adapters.h]hoThe “FlashPointFirst” option forces FlashPoint Host Adapters to be probed before MultiMaster Host Adapters.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hXvThe BusLogic Driver Tagged Queuing Options allow for explicitly specifying the Queue Depth and whether Tagged Queuing is permitted for each Target Device (assuming that the Target Device supports Tagged Queuing). The Queue Depth is the number of SCSI Commands that are allowed to be concurrently presented for execution (either to the Host Adapter or Target Device). Note that explicitly enabling Tagged Queuing may lead to problems; the option to enable or disable Tagged Queuing is provided primarily to allow disabling Tagged Queuing on Target Devices that do not implement it correctly. The following options are available:h]hXvThe BusLogic Driver Tagged Queuing Options allow for explicitly specifying the Queue Depth and whether Tagged Queuing is permitted for each Target Device (assuming that the Target Device supports Tagged Queuing). The Queue Depth is the number of SCSI Commands that are allowed to be concurrently presented for execution (either to the Host Adapter or Target Device). Note that explicitly enabling Tagged Queuing may lead to problems; the option to enable or disable Tagged Queuing is provided primarily to allow disabling Tagged Queuing on Target Devices that do not implement it correctly. The following options are available:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hQueueDepth:h]hQueueDepth:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hXThe "QueueDepth:" or QD:" option specifies the Queue Depth to use for all Target Devices that support Tagged Queuing, as well as the maximum Queue Depth for devices that do not support Tagged Queuing. If no Queue Depth option is provided, the Queue Depth will be determined automatically based on the Host Adapter's Total Queue Depth and the number, type, speed, and capabilities of the detected Target Devices. Target Devices that do not support Tagged Queuing always have their Queue Depth set to BusLogic_UntaggedQueueDepth or BusLogic_UntaggedQueueDepthBB, unless a lower Queue Depth option is provided. A Queue Depth of 1 automatically disables Tagged Queuing. h]h)}(hXThe "QueueDepth:" or QD:" option specifies the Queue Depth to use for all Target Devices that support Tagged Queuing, as well as the maximum Queue Depth for devices that do not support Tagged Queuing. If no Queue Depth option is provided, the Queue Depth will be determined automatically based on the Host Adapter's Total Queue Depth and the number, type, speed, and capabilities of the detected Target Devices. Target Devices that do not support Tagged Queuing always have their Queue Depth set to BusLogic_UntaggedQueueDepth or BusLogic_UntaggedQueueDepthBB, unless a lower Queue Depth option is provided. A Queue Depth of 1 automatically disables Tagged Queuing.h]hXThe “QueueDepth:” or QD:” option specifies the Queue Depth to use for all Target Devices that support Tagged Queuing, as well as the maximum Queue Depth for devices that do not support Tagged Queuing. If no Queue Depth option is provided, the Queue Depth will be determined automatically based on the Host Adapter’s Total Queue Depth and the number, type, speed, and capabilities of the detected Target Devices. Target Devices that do not support Tagged Queuing always have their Queue Depth set to BusLogic_UntaggedQueueDepth or BusLogic_UntaggedQueueDepthBB, unless a lower Queue Depth option is provided. A Queue Depth of 1 automatically disables Tagged Queuing.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(h#QueueDepth:[,...]h]h#QueueDepth:[,...]}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hThe "QueueDepth:[...]" or "QD:[...]" option specifies the Queue Depth individually for each Target Device. If an is omitted, the associated Target Device will have its Queue Depth selected automatically. h]h)}(hThe "QueueDepth:[...]" or "QD:[...]" option specifies the Queue Depth individually for each Target Device. If an is omitted, the associated Target Device will have its Queue Depth selected automatically.h]hThe “QueueDepth:[...]” or “QD:[...]” option specifies the Queue Depth individually for each Target Device. If an is omitted, the associated Target Device will have its Queue Depth selected automatically.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hTaggedQueuing:Defaulth]hTaggedQueuing:Default}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hThe "TaggedQueuing:Default" or "TQ:Default" option permits Tagged Queuing based on the firmware version of the BusLogic Host Adapter and based on whether the Queue Depth allows queuing multiple commands. h]h)}(hThe "TaggedQueuing:Default" or "TQ:Default" option permits Tagged Queuing based on the firmware version of the BusLogic Host Adapter and based on whether the Queue Depth allows queuing multiple commands.h]hThe “TaggedQueuing:Default” or “TQ:Default” option permits Tagged Queuing based on the firmware version of the BusLogic Host Adapter and based on whether the Queue Depth allows queuing multiple commands.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hTaggedQueuing:Enableh]hTaggedQueuing:Enable}(hj2hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hThe "TaggedQueuing:Enable" or "TQ:Enable" option enables Tagged Queuing for all Target Devices on this Host Adapter, overriding any limitation that would otherwise be imposed based on the Host Adapter firmware version. h]h)}(hThe "TaggedQueuing:Enable" or "TQ:Enable" option enables Tagged Queuing for all Target Devices on this Host Adapter, overriding any limitation that would otherwise be imposed based on the Host Adapter firmware version.h]hThe “TaggedQueuing:Enable” or “TQ:Enable” option enables Tagged Queuing for all Target Devices on this Host Adapter, overriding any limitation that would otherwise be imposed based on the Host Adapter firmware version.}(hjDhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj@ubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hTaggedQueuing:Disableh]hTaggedQueuing:Disable}(hjXhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hxThe "TaggedQueuing:Disable" or "TQ:Disable" option disables Tagged Queuing for all Target Devices on this Host Adapter. h]h)}(hwThe "TaggedQueuing:Disable" or "TQ:Disable" option disables Tagged Queuing for all Target Devices on this Host Adapter.h]hThe “TaggedQueuing:Disable” or “TQ:Disable” option disables Tagged Queuing for all Target Devices on this Host Adapter.}(hjjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjfubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hTaggedQueuing:h]hTaggedQueuing:}(hj~hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hXThe "TaggedQueuing:" or "TQ:" option controls Tagged Queuing individually for each Target Device. is a sequence of "Y", "N", and "X" characters. "Y" enables Tagged Queuing, "N" disables Tagged Queuing, and "X" accepts the default based on the firmware version. The first character refers to Target Device 0, the second to Target Device 1, and so on; if the sequence of "Y", "N", and "X" characters does not cover all the Target Devices, unspecified characters are assumed to be "X". h]h)}(hX The "TaggedQueuing:" or "TQ:" option controls Tagged Queuing individually for each Target Device. is a sequence of "Y", "N", and "X" characters. "Y" enables Tagged Queuing, "N" disables Tagged Queuing, and "X" accepts the default based on the firmware version. The first character refers to Target Device 0, the second to Target Device 1, and so on; if the sequence of "Y", "N", and "X" characters does not cover all the Target Devices, unspecified characters are assumed to be "X".h]hX=The “TaggedQueuing:” or “TQ:” option controls Tagged Queuing individually for each Target Device. is a sequence of “Y”, “N”, and “X” characters. “Y” enables Tagged Queuing, “N” disables Tagged Queuing, and “X” accepts the default based on the firmware version. The first character refers to Target Device 0, the second to Target Device 1, and so on; if the sequence of “Y”, “N”, and “X” characters does not cover all the Target Devices, unspecified characters are assumed to be “X”.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hAThe BusLogic Driver Miscellaneous Options comprise the following:h]hAThe BusLogic Driver Miscellaneous Options comprise the following:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hBusSettleTime:h]hBusSettleTime:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hX$The "BusSettleTime:" or "BST:" option specifies the Bus Settle Time in seconds. The Bus Settle Time is the amount of time to wait between a Host Adapter Hard Reset which initiates a SCSI Bus Reset and issuing any SCSI Commands. If unspecified, it defaults to BusLogic_DefaultBusSettleTime. h]h)}(hX#The "BusSettleTime:" or "BST:" option specifies the Bus Settle Time in seconds. The Bus Settle Time is the amount of time to wait between a Host Adapter Hard Reset which initiates a SCSI Bus Reset and issuing any SCSI Commands. If unspecified, it defaults to BusLogic_DefaultBusSettleTime.h]hX+The “BusSettleTime:” or “BST:” option specifies the Bus Settle Time in seconds. The Bus Settle Time is the amount of time to wait between a Host Adapter Hard Reset which initiates a SCSI Bus Reset and issuing any SCSI Commands. If unspecified, it defaults to BusLogic_DefaultBusSettleTime.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hInhibitTargetInquiryh]hInhibitTargetInquiry}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hXThe "InhibitTargetInquiry" option inhibits the execution of an Inquire Target Devices or Inquire Installed Devices command on MultiMaster Host Adapters. This may be necessary with some older Target Devices that do not respond correctly when Logical Units above 0 are addressed. h]h)}(hXThe "InhibitTargetInquiry" option inhibits the execution of an Inquire Target Devices or Inquire Installed Devices command on MultiMaster Host Adapters. This may be necessary with some older Target Devices that do not respond correctly when Logical Units above 0 are addressed.h]hXThe “InhibitTargetInquiry” option inhibits the execution of an Inquire Target Devices or Inquire Installed Devices command on MultiMaster Host Adapters. This may be necessary with some older Target Devices that do not respond correctly when Logical Units above 0 are addressed.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(h=The BusLogic Driver Debugging Options comprise the following:h]h=The BusLogic Driver Debugging Options comprise the following:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(h TraceProbeh]h TraceProbe}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hAThe "TraceProbe" option enables tracing of Host Adapter Probing. h]h)}(h@The "TraceProbe" option enables tracing of Host Adapter Probing.h]hDThe “TraceProbe” option enables tracing of Host Adapter Probing.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hTraceHardwareReseth]hTraceHardwareReset}(hj2hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hPThe "TraceHardwareReset" option enables tracing of Host Adapter Hardware Reset. h]h)}(hOThe "TraceHardwareReset" option enables tracing of Host Adapter Hardware Reset.h]hSThe “TraceHardwareReset” option enables tracing of Host Adapter Hardware Reset.}(hjDhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhj@ubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hTraceConfigurationh]hTraceConfiguration}(hjXhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hOThe "TraceConfiguration" option enables tracing of Host Adapter Configuration. h]h)}(hNThe "TraceConfiguration" option enables tracing of Host Adapter Configuration.h]hRThe “TraceConfiguration” option enables tracing of Host Adapter Configuration.}(hjjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjfubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(h TraceErrorsh]h TraceErrors}(hj~hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hThe "TraceErrors" option enables tracing of SCSI Commands that return an error from the Target Device. The CDB and Sense Data will be printed for each SCSI Command that fails. h]h)}(hThe "TraceErrors" option enables tracing of SCSI Commands that return an error from the Target Device. The CDB and Sense Data will be printed for each SCSI Command that fails.h]hThe “TraceErrors” option enables tracing of SCSI Commands that return an error from the Target Device. The CDB and Sense Data will be printed for each SCSI Command that fails.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hDebugh]hDebug}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM hjhhubh)}(h2The "Debug" option enables all debugging options. h]h)}(h1The "Debug" option enables all debugging options.h]h5The “Debug” option enables all debugging options.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hXThe following examples demonstrate setting the Queue Depth for Target Devices 1 and 2 on the first host adapter to 7 and 15, the Queue Depth for all Target Devices on the second host adapter to 31, and the Bus Settle Time on the second host adapter to 30 seconds.h]hXThe following examples demonstrate setting the Queue Depth for Target Devices 1 and 2 on the first host adapter to 7 and 15, the Queue Depth for all Target Devices on the second host adapter to 31, and the Bus Settle Time on the second host adapter to 30 seconds.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh)}(hLinux Kernel Command Line::h]hLinux Kernel Command Line:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubh literal_block)}(h@linux BusLogic=QueueDepth:[,7,15];QueueDepth:31,BusSettleTime:30h]h@linux BusLogic=QueueDepth:[,7,15];QueueDepth:31,BusSettleTime:30}hjsbah}(h]h ]h"]h$]h&]hhuh1jhhhMhjhhubh)}(h,LILO Linux Boot Loader (in /etc/lilo.conf)::h]h+LILO Linux Boot Loader (in /etc/lilo.conf):}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubj)}(hEappend = "BusLogic=QueueDepth:[,7,15];QueueDepth:31,BusSettleTime:30"h]hEappend = "BusLogic=QueueDepth:[,7,15];QueueDepth:31,BusSettleTime:30"}hjsbah}(h]h ]h"]h$]h&]hhuh1jhhhMhjhhubh)}(h5INSMOD Loadable Kernel Module Installation Facility::h]h4INSMOD Loadable Kernel Module Installation Facility:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhMhjhhubj)}(hVinsmod BusLogic.o \ 'BusLogic="QueueDepth:[,7,15];QueueDepth:31,BusSettleTime:30"'h]hVinsmod BusLogic.o \ 'BusLogic="QueueDepth:[,7,15];QueueDepth:31,BusSettleTime:30"'}hj sbah}(h]h ]h"]h$]h&]hhuh1jhhhMhjhhubhnote)}(heModule Utilities 2.1.71 or later is required for correct parsing of driver options containing commas.h]h)}(heModule Utilities 2.1.71 or later is required for correct parsing of driver options containing commas.h]heModule Utilities 2.1.71 or later is required for correct parsing of driver options containing commas.}(hj4hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM%hj0ubah}(h]h ]h"]h$]h&]uh1j.hjhhhhhNubeh}(h]driver-optionsah ]h"]driver optionsah$]h&]uh1hhhhhhhhMubh)}(hhh](h)}(hDriver Installationh]hDriver Installation}(hjShhhNhNubah}(h]h ]h"]h$]h&]uh1hhjPhhhhhM*ubh)}(hThis distribution was prepared for Linux kernel version 2.0.35, but should be compatible with 2.0.4 or any later 2.0 series kernel.h]hThis distribution was prepared for Linux kernel version 2.0.35, but should be compatible with 2.0.4 or any later 2.0 series kernel.}(hjahhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM,hjPhhubh)}(hTo install the new BusLogic SCSI driver, you may use the following commands, replacing "/usr/src" with wherever you keep your Linux kernel source tree::h]hTo install the new BusLogic SCSI driver, you may use the following commands, replacing “/usr/src” with wherever you keep your Linux kernel source tree:}(hjohhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM/hjPhhubj)}(hcd /usr/src tar -xvzf BusLogic-2.0.15.tar.gz mv README.* LICENSE.* BusLogic.[ch] FlashPoint.c linux/drivers/scsi patch -p0 < BusLogic.patch (only for 2.0.33 and below) cd linux make config make zImageh]hcd /usr/src tar -xvzf BusLogic-2.0.15.tar.gz mv README.* LICENSE.* BusLogic.[ch] FlashPoint.c linux/drivers/scsi patch -p0 < BusLogic.patch (only for 2.0.33 and below) cd linux make config make zImage}hj}sbah}(h]h ]h"]h$]h&]hhuh1jhhhM2hjPhhubh)}(haThen install "arch/x86/boot/zImage" as your standard kernel, run lilo if appropriate, and reboot.h]heThen install “arch/x86/boot/zImage” as your standard kernel, run lilo if appropriate, and reboot.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhM:hjPhhubeh}(h]driver-installationah ]h"]driver installationah$]h&]uh1hhhhhhhhM*ubh)}(hhh](h)}(h#BusLogic Announcements Mailing Listh]h#BusLogic Announcements Mailing List}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhM?ubh)}(hX@The BusLogic Announcements Mailing List provides a forum for informing Linux users of new driver releases and other announcements regarding Linux support for BusLogic SCSI Host Adapters. To join the mailing list, send a message to "buslogic-announce-request@dandelion.com" with the line "subscribe" in the message body.h](hThe BusLogic Announcements Mailing List provides a forum for informing Linux users of new driver releases and other announcements regarding Linux support for BusLogic SCSI Host Adapters. To join the mailing list, send a message to “}(hjhhhNhNubjT)}(h'buslogic-announce-request@dandelion.comh]h'buslogic-announce-request@dandelion.com}(hjhhhNhNubah}(h]h ]h"]h$]h&]refuri.mailto:buslogic-announce-request@dandelion.comuh1jShjubh6” with the line “subscribe” in the message body.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhMAhjhhubeh}(h]#buslogic-announcements-mailing-listah ]h"]#buslogic announcements mailing listah$]h&]uh1hhhhhhhhM?ubeh}(h]9buslogic-multimaster-and-flashpoint-scsi-driver-for-linuxah ]h"]9buslogic multimaster and flashpoint scsi driver for linuxah$]h&]uh1hhhhhhhhKubeh}(h]h ]h"]h$]h&]sourcehuh1hcurrent_sourceN current_lineNsettingsdocutils.frontendValues)}(hN generatorN datestampN source_linkN source_urlN toc_backlinksjfootnote_backlinksK sectnum_xformKstrip_commentsNstrip_elements_with_classesN strip_classesN report_levelK halt_levelKexit_status_levelKdebugNwarning_streamN tracebackinput_encoding utf-8-siginput_encoding_error_handlerstrictoutput_encodingutf-8output_encoding_error_handlerjerror_encodingutf-8error_encoding_error_handlerbackslashreplace language_codeenrecord_dependenciesNconfigN id_prefixhauto_id_prefixid dump_settingsNdump_internalsNdump_transformsNdump_pseudo_xmlNexpose_internalsNstrict_visitorN_disable_configN_sourcehnj _destinationN _config_files]7/var/lib/git/docbuild/linux/Documentation/docutils.confafile_insertion_enabled raw_enabledKline_length_limitM'pep_referencesN pep_base_urlhttps://peps.python.org/pep_file_url_templatepep-%04drfc_referencesN rfc_base_url&https://datatracker.ietf.org/doc/html/ tab_widthKtrim_footnote_reference_spacesyntax_highlightlong smart_quotessmartquotes_locales]character_level_inline_markupdoctitle_xform docinfo_xformKsectsubtitle_xform image_loadinglinkembed_stylesheetcloak_email_addressessection_self_linkenvNubreporterNindirect_targets]substitution_defs}substitution_names}refnames}refids}nameids}(jjjjjjjjjjjjj1j.jbj_jjje jb j j j j enabling ultrascsi transfersNjjj?j<jjjMjJjjjju nametypes}(jjjjjjj1jbjje j j jJjj?jjMjjuh}(jhjjjjjjjjjjj.jj_j4jjejb jj jh j jy j j jj j<jjjBjjjJjjjPjju footnote_refs} citation_refs} autofootnotes]autofootnote_refs]symbol_footnotes]symbol_footnote_refs] footnotes] citations]autofootnote_startKsymbol_footnote_startK id_counter collectionsCounter}jKsRparse_messages]hsystem_message)}(hhh]h)}(h?Duplicate implicit target name: "enabling ultrascsi transfers".h]hCDuplicate implicit target name: “enabling ultrascsi transfers”.}(hjnhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjkubah}(h]h ]h"]h$]h&]jalevelKtypeINFOsourcehnjlineMquh1jihjhhhhhMqubatransform_messages] transformerN include_log] decorationNhhub.