The buson, busoff values refer to the number of
microseconds that the card dominates the ISA bus. The defaults
are 11us on, and 4us off, so that other cards (such as an ISA
LANCE Ethernet card) have a chance to get access to the ISA bus.

Значения buson, busoff

The dmaspeed value refers to the rate (in MB/s)
at which the DMA (Direct Memory Access) transfers proceed at. The
default is 5MB/s. Newer revision cards allow you to select this
value as part of the soft-configuration, older cards use jumpers.
You can use values up to 10MB/s assuming that your motherboard is
capable of handling it. Experiment with caution if using values
over 5MB/s.

Adaptec aha274x, aha284x, aic7xxx (`aic7xxx=')

These boards can accept an argument of the form:

aic7xxx=extended,no_reset

The extended value, if non-zero, indicates that
extended translation for large disks is enabled. The no_reset
value, if non-zero, tells the driver not to reset the SCSI bus
when setting up the host adaptor at boot.

AdvanSys SCSI Host Adaptors (`advansys=')

The AdvanSys driver can accept up to four i/o addresses that
will be probed for an AdvanSys SCSI card. Note that these values
(if used) do not effect EISA or PCI probing in any way. They are
only used for probing ISA and VLB cards. In addition, if the
driver has been compiled with debugging enabled, the level of
debugging output can be set by adding an 0xdeb[0-f]
parameter. The 0-f allows setting the level of the
debugging messages to any of 16 levels of verbosity.

Always IN2000 Host Adaptor (`in2000=')

Unlike other SCSI host boot arguments, the IN2000 driver uses
ASCII string prefixes for most of its integer arguments. Here is
a list of the supported arguments:

ioport:addr -- Where addr is IO address of a (usually
ROM-less) card.

noreset -- No optional args. Prevents SCSI bus reset at boot
time.

nosync:x -- x is a bitmask where the 1st 7 bits correspond
with the 7 possible SCSI devices (bit 0 for device #0, etc). Set
a bit to PREVENT sync negotiation on that device. The driver
default is sync DISABLED on all devices.

period:ns -- ns is the minimum # of nanoseconds in a SCSI data
transfer period. Default is 500; acceptable values are 250 to
1000.

disconnect:x -- x = 0 to never allow disconnects, 2 to always
allow them. x = 1 does 'adaptive' disconnects, which is the
default and generally the best choice.

debug:x If `DEBUGGING_ON' is defined, x is a bitmask that
causes various types of debug output to printed - see the DB_xxx
defines in in2000.h

proc:x -- If `PROC_INTERFACE' is defined, x is a bitmask that
determines how the /proc interface works and what it does - see
the PR_xxx defines in in2000.h

AMD AM53C974 based hardware (`AM53C974=')

Unlike other drivers, this one does not use boot parameters to
communicate i/o, IRQ or DMA channels. (Since the AM53C974 is a
PCI device, there shouldn't be a need to do so.) Instead, the
parameters are used to communicate the transfer modes and rates
that are to be used between the host and the target device. This
is best described with an example:

AM53C974=7,2,8,15

This would be interpreted as follows: `For communication
between the controller with SCSI-ID 7 and the device with SCSI-ID
2, a transfer rate of 8MHz in synchronous mode with max. 15 bytes
offset should be negotiated.' More details can be found in the
file linux/drivers/scsi/README.AM53C974

BusLogic SCSI Hosts with v1.2 kernels (`buslogic=')

In older kernels, the buslogic driver accepts only one
parameter, that being the I/O base. It expects that to be one of
the following valid values: 0x130, 0x134, 0x230, 0x234,
0x330, 0x334.

BusLogic SCSI Hosts with v2.x kernels (`BusLogic=')

With v2.x kernels, the BusLogic driver accepts many
parameters. (Note the case in the above; upper case B and L!!!).
There are simply too many to list here. A complete description is
tucked away in the middle of the driver linux/drivers/scsi/BusLogic.c
and searching for the string BusLogic= will put you
right on it.

EATA SCSI Cards (`eata=')

As of late v2.0 kernels, the EATA drivers will accept a boot
argument to specify the i/o base(s) to be probed. It is of the
form:

eata=iobase1[,iobase2][,iobase3]...[,iobaseN]

The driver will probe the addresses in the order that they are
listed.

Future Domain TMC-8xx, TMC-950 (`tmc8xx=')

The probe code for these SCSI hosts looks for an installed
BIOS, and if none is present, the probe will not find your card.
Or, if the signature string of your BIOS is not recognized then
it will also not be found. In either case, you will then have to
use a boot argument of the form:

tmc8xx=mem_base,irq

The mem_base value is the value of the memory
mapped I/O region that the card uses. This will usually be one of
the following values: 0xc8000, 0xca000, 0xcc000, 0xce000,
0xdc000, 0xde000.

Future Domain TMC-16xx, TMC-3260, AHA-2920 (`fdomain=')

The driver detects these cards according to a list of known
BIOS ROM signatures. For a full list of known BIOS revisions,
please see linux/drivers/scsi/fdomain.c as it has a
lot of information at the top of that file. If your BIOS is not
known to the driver, you can use an override of the form:

fdomain=iobase,irq[,scsi_id]

IOMEGA Parallel Port / ZIP drive (`ppa=')

This driver is for the IOMEGA Parallel Port SCSI adapter which
is embedded into the IOMEGA ZIP drives. It may also work with the
original IOMEGA PPA3 device. The boot argument for this driver is
of the form:

ppa=iobase,speed_high,speed_low,nybble

with all but iobase being optionally specified values. If you
wish to alter any of the three optional parameters, you are
advised to read linux/drivers/scsi/README.ppa for
details of what they control.

NCR5380 based controllers (`ncr5380=')

Depending on your board, the 5380 can be either i/o mapped or
memory mapped. (An address below 0x400 usually implies i/o
mapping, but PCI and EISA hardware use i/o addresses above
0x3ff.) In either case, you specify the address, the IRQ value
and the DMA channel value. An example for an i/o mapped card
would be: ncr5380=0x350,5,3. If the card doesn't use
interrupts, then an IRQ value of 255 (0xff) will
disable interrupts. An IRQ value of 254 means to autoprobe. More
details can be found in the file linux/drivers/scsi/README.g_NCR5380

NCR53c400 based controllers (`ncr53c400=')

The generic 53c400 support is done with the same driver as the
generic 5380 support mentioned above. The boot argument is
identical to the above with the exception that no DMA channel is
used by the 53c400.

NCR53c406a based controllers (`ncr53c406a=')

This driver uses a boot argument of the form:

ncr53c406a=PORTBASE,IRQ,FASTPIO

where the IRQ and FASTPIO parameters are optional. An
interrupt value of zero disables the use of interrupts. Using a
value of one for the FASTPIO parameter enables the use of insl
and outsl instructions instead of the single-byte inb
and outb instructions. The driver can also use DMA
as a compile-time option.

Pro Audio Spectrum (`pas16=')

The PAS16 uses a NCR5380 SCSI chip, and newer models support
jumper-less configuration. The boot argument is of the form:

pas16=iobase,irq

The only difference is that you can specify an IRQ value of
255, which will tell the driver to work without using interrupts,
albeit at a performance loss. The iobase is usually 0x388.

Seagate ST-0x (`st0x=')

The probe code for these SCSI hosts looks for an installed
BIOS, and if none is present, the probe will not find your card.
Or, if the signature string of your BIOS is not recognized then
it will also not be found. In either case, you will then have to
use a boot argument of the form:

st0x=mem_base,irq

The mem_base value is the value of the memory
mapped I/O region that the card uses. This will usually be one of
the following values: 0xc8000, 0xca000, 0xcc000, 0xce000,
0xdc000, 0xde000.

Trantor T128 (`t128=')

These cards are also based on the NCR5380 chip, and accept the
following options:

t128=mem_base,irq

The valid values for mem_base are as follows: 0xcc000,
0xc8000, 0xdc000, 0xd8000.

Ultrastor SCSI cards (`u14-34f=')

Note that there appears to be two independent drivers for this
card, namely CONFIG_SCSI_U14_34F that uses u14-34f.c
and CONFIG_SCSI_ULTRASTOR that uses ultrastor.c.
It is the u14-34f one that (as of late v2.0 kernels) accepts a
boot argument of the form:

u14-34f=iobase1[,iobase2][,iobase3]...[,iobaseN]

The driver will probe the addresses in the order that they are
listed.

Western Digital WD7000 cards (`wd7000=')

The driver probe for the wd7000 looks for a known BIOS ROM
string and knows about a few standard configuration settings. If
it doesn't come up with the correct values for your card, or you
have an unrecognized BIOS version, you can use a boot argument of
the form: