2006-12-20 01:58:27 +01:00
|
|
|
# -*- shell-script -*-
|
|
|
|
|
2006-12-31 17:20:20 +01:00
|
|
|
comment "An alternative FireWire stack is available with EXPERIMENTAL=y"
|
2006-12-28 16:20:00 +01:00
|
|
|
depends on EXPERIMENTAL=n
|
|
|
|
|
2007-03-18 01:39:28 +01:00
|
|
|
config FIREWIRE
|
2006-12-28 16:20:00 +01:00
|
|
|
tristate "IEEE 1394 (FireWire) support (JUJU alternative stack, experimental)"
|
|
|
|
depends on EXPERIMENTAL
|
2007-05-08 02:33:31 +02:00
|
|
|
select CRC_ITU_T
|
2006-12-20 01:58:27 +01:00
|
|
|
help
|
|
|
|
IEEE 1394 describes a high performance serial bus, which is also
|
|
|
|
known as FireWire(tm) or i.Link(tm) and is used for connecting all
|
|
|
|
sorts of devices (most notably digital video cameras) to your
|
|
|
|
computer.
|
|
|
|
|
|
|
|
If you have FireWire hardware and want to use it, say Y here. This
|
|
|
|
is the core support only, you will also need to select a driver for
|
|
|
|
your IEEE 1394 adapter.
|
|
|
|
|
2007-01-07 22:33:59 +01:00
|
|
|
To compile this driver as a module, say M here: the module will be
|
2007-05-25 13:54:49 +02:00
|
|
|
called firewire-core.
|
2006-12-20 01:58:27 +01:00
|
|
|
|
2007-01-07 22:33:59 +01:00
|
|
|
This is the "JUJU" FireWire stack, an alternative implementation
|
|
|
|
designed for robustness and simplicity. You can build either this
|
|
|
|
stack, or the classic stack (the ieee1394 driver, ohci1394 etc.)
|
|
|
|
or both.
|
2006-12-20 01:58:27 +01:00
|
|
|
|
2007-03-18 01:39:28 +01:00
|
|
|
config FIREWIRE_OHCI
|
2007-01-04 18:35:00 +01:00
|
|
|
tristate "Support for OHCI FireWire host controllers"
|
2007-03-18 01:39:28 +01:00
|
|
|
depends on PCI && FIREWIRE
|
2006-12-20 01:58:35 +01:00
|
|
|
help
|
2007-01-04 18:35:00 +01:00
|
|
|
Enable this driver if you have a FireWire controller based
|
2006-12-20 01:58:35 +01:00
|
|
|
on the OHCI specification. For all practical purposes, this
|
|
|
|
is the only chipset in use, so say Y here.
|
|
|
|
|
2007-01-07 22:33:59 +01:00
|
|
|
To compile this driver as a module, say M here: The module will be
|
2007-05-25 13:54:49 +02:00
|
|
|
called firewire-ohci.
|
2007-01-07 22:33:59 +01:00
|
|
|
|
|
|
|
If you also build ohci1394 of the classic IEEE 1394 driver stack,
|
2007-05-25 13:54:49 +02:00
|
|
|
blacklist either ohci1394 or firewire-ohci to let hotplug load the
|
|
|
|
desired driver.
|
2006-12-20 01:58:35 +01:00
|
|
|
|
2007-03-18 01:39:28 +01:00
|
|
|
config FIREWIRE_SBP2
|
2006-12-20 01:58:40 +01:00
|
|
|
tristate "Support for storage devices (SBP-2 protocol driver)"
|
2007-03-18 01:39:28 +01:00
|
|
|
depends on FIREWIRE && SCSI
|
2006-12-20 01:58:40 +01:00
|
|
|
help
|
2007-01-04 18:35:00 +01:00
|
|
|
This option enables you to use SBP-2 devices connected to a
|
|
|
|
FireWire bus. SBP-2 devices include storage devices like
|
2006-12-20 01:58:40 +01:00
|
|
|
harddisks and DVD drives, also some other FireWire devices
|
|
|
|
like scanners.
|
|
|
|
|
2007-01-07 22:33:59 +01:00
|
|
|
To compile this driver as a module, say M here: The module will be
|
2007-05-25 13:54:49 +02:00
|
|
|
called firewire-sbp2.
|
2007-01-07 22:33:59 +01:00
|
|
|
|
2006-12-20 01:58:40 +01:00
|
|
|
You should also enable support for disks, CD-ROMs, etc. in the SCSI
|
|
|
|
configuration section.
|
|
|
|
|
2007-01-07 22:33:59 +01:00
|
|
|
If you also build sbp2 of the classic IEEE 1394 driver stack,
|
2007-05-25 13:54:49 +02:00
|
|
|
blacklist either sbp2 or firewire-sbp2 to let hotplug load the
|
|
|
|
desired driver.
|
2007-01-07 22:33:59 +01:00
|
|
|
|