2 tristate "Legacy alternative FireWire driver stack"
3 depends on PCI || BROKEN
5 IEEE 1394 describes a high performance serial bus, which is also
6 known as FireWire(tm) or i.Link(tm) and is used for connecting all
7 sorts of devices (most notably digital video cameras) to your
10 If you have FireWire hardware and want to use it, say Y here. This
11 is the core support only, you will also need to select a driver for
12 your IEEE 1394 adapter.
14 To compile this driver as a module, say M here: the module will be
18 ieee1394 is superseded by the newer firewire-core driver. See
19 http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for
20 further information on how to switch to the new FireWire drivers.
22 config IEEE1394_OHCI1394
23 tristate "OHCI-1394 controllers"
24 depends on PCI && IEEE1394
26 Enable this driver if you have an IEEE 1394 controller based on the
27 OHCI-1394 specification. The current driver is only tested with OHCI
28 chipsets made by Texas Instruments and NEC. Most third-party vendors
29 use one of these chipsets. It should work with any OHCI-1394
30 compliant card, however.
32 To compile this driver as a module, say M here: the module will be
36 ohci1394 is superseded by the newer firewire-ohci driver. See
37 http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for
38 further information on how to switch to the new FireWire drivers.
40 If you want to install firewire-ohci and ohci1394 together, you
41 should configure them only as modules and blacklist the driver(s)
42 which you don't want to have auto-loaded. Add either
48 blacklist firewire-ohci
50 to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf
51 depending on your distribution.
53 comment "PCILynx controller requires I2C"
54 depends on IEEE1394 && I2C=n
56 config IEEE1394_PCILYNX
57 tristate "PCILynx controller"
58 depends on PCI && IEEE1394 && I2C
61 Say Y here if you have an IEEE-1394 controller with the Texas
62 Instruments PCILynx chip. Note: this driver is written for revision
63 2 of this chip and may not work with revision 0.
65 To compile this driver as a module, say M here: the module will be
68 Only some old and now very rare PCI and CardBus cards and
69 PowerMacs G3 B&W contain the PCILynx controller. Therefore
70 almost everybody can say N here.
72 comment "SBP-2 support (for storage devices) requires SCSI"
73 depends on IEEE1394 && SCSI=n
76 tristate "Storage devices (SBP-2 protocol)"
77 depends on IEEE1394 && SCSI
79 This option enables you to use SBP-2 devices connected to an IEEE
80 1394 bus. SBP-2 devices include storage devices like harddisks and
81 DVD drives, also some other FireWire devices like scanners.
83 You should also enable support for disks, CD-ROMs, etc. in the SCSI
84 configuration section.
86 To compile this driver as a module, say M here: the module will be
90 sbp2 is superseded by the newer firewire-sbp2 driver. See
91 http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for
92 further information on how to switch to the new FireWire drivers.
94 config IEEE1394_SBP2_PHYS_DMA
95 bool "Enable replacement for physical DMA in SBP2"
96 depends on IEEE1394_SBP2 && VIRT_TO_BUS && EXPERIMENTAL
98 This builds sbp2 for use with non-OHCI host adapters which do not
99 support physical DMA or for when ohci1394 is run with phys_dma=0.
100 Physical DMA is data movement without assistance of the drivers'
101 interrupt handlers. This option includes the interrupt handlers
102 that are required in absence of this hardware feature.
104 This option is buggy and currently broken on some architectures.
107 config IEEE1394_ETH1394_ROM_ENTRY
112 config IEEE1394_ETH1394
113 tristate "IP networking over 1394 (experimental)"
114 depends on IEEE1394 && EXPERIMENTAL && INET
115 select IEEE1394_ETH1394_ROM_ENTRY
117 This driver implements a functional majority of RFC 2734: IPv4 over
118 1394. It will provide IP connectivity with implementations of RFC
119 2734 found on other operating systems. It will not communicate with
120 older versions of this driver found in stock kernels prior to 2.6.3.
121 This driver is still considered experimental. It does not yet support
122 MCAP, therefore multicast support is significantly limited.
124 The module is called eth1394 although it does not emulate Ethernet.
127 eth1394 is superseded by the newer firewire-net driver. See
128 http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for
129 further information on how to switch to the new FireWire drivers.
131 config IEEE1394_RAWIO
132 tristate "raw1394 userspace interface"
135 This option adds support for the raw1394 device file which enables
136 direct communication of user programs with IEEE 1394 devices
137 (isochronous and asynchronous). Almost all application programs
138 which access FireWire require this option.
140 To compile this driver as a module, say M here: the module will be
144 raw1394 is superseded by the newer firewire-core driver. See
145 http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for
146 further information on how to switch to the new FireWire drivers.
148 config IEEE1394_VIDEO1394
149 tristate "video1394 userspace interface"
150 depends on IEEE1394 && IEEE1394_OHCI1394
152 This option adds support for the video1394 device files which enable
153 isochronous communication of user programs with IEEE 1394 devices,
154 especially video capture or export. This interface is used by all
155 libdc1394 based programs and by several other programs, in addition to
156 the raw1394 interface. It is generally not required for DV capture.
158 To compile this driver as a module, say M here: the module will be
162 video1394 is superseded by the newer firewire-core driver. See
163 http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for
164 further information on how to switch to the new FireWire drivers.
166 config IEEE1394_DV1394
167 tristate "dv1394 userspace interface (deprecated)"
168 depends on IEEE1394 && IEEE1394_OHCI1394
170 The dv1394 driver is unsupported and may be removed from Linux in a
171 future release. Its functionality is now provided by either
172 raw1394 or firewire-core together with libraries such as libiec61883.
174 config IEEE1394_VERBOSEDEBUG
175 bool "Excessive debugging output"
178 If you say Y here, you will get very verbose debugging logs from the
179 ieee1394 drivers, including sent and received packet headers. This
180 will quickly result in large amounts of data sent to the system log.
182 Say Y if you really need the debugging output. Everyone else says N.