1 menu "IEEE 1394 (FireWire) support"
2 depends on PCI || BROKEN
5 tristate "IEEE 1394 (FireWire) support"
6 depends on PCI || BROKEN
8 IEEE 1394 describes a high performance serial bus, which is also
9 known as FireWire(tm) or i.Link(tm) and is used for connecting all
10 sorts of devices (most notably digital video cameras) to your
13 If you have FireWire hardware and want to use it, say Y here. This
14 is the core support only, you will also need to select a driver for
15 your IEEE 1394 adapter.
17 To compile this driver as a module, say M here: the
18 module will be called ieee1394.
20 comment "Subsystem Options"
23 config IEEE1394_VERBOSEDEBUG
24 bool "Excessive debugging output"
27 If you say Y here, you will get very verbose debugging logs from
28 the subsystem which includes a dump of the header of every sent
29 and received packet. This can amount to a high amount of data
30 collected in a very short time which is usually also saved to
31 disk by the system logging daemons.
33 Say Y if you really want or need the debugging output, everyone
39 comment "Texas Instruments PCILynx requires I2C"
40 depends on IEEE1394 && I2C=n
42 config IEEE1394_PCILYNX
43 tristate "Texas Instruments PCILynx support"
44 depends on PCI && IEEE1394 && I2C
47 Say Y here if you have an IEEE-1394 controller with the Texas
48 Instruments PCILynx chip. Note: this driver is written for revision
49 2 of this chip and may not work with revision 0.
51 To compile this driver as a module, say M here: the
52 module will be called pcilynx.
54 Only some old and now very rare PCI and CardBus cards and
55 PowerMacs G3 B&W contain the PCILynx controller. Therefore
56 almost everybody can say N here.
58 config IEEE1394_OHCI1394
59 tristate "OHCI-1394 support"
60 depends on PCI && IEEE1394
62 Enable this driver if you have an IEEE 1394 controller based on the
63 OHCI-1394 specification. The current driver is only tested with OHCI
64 chipsets made by Texas Instruments and NEC. Most third-party vendors
65 use one of these chipsets. It should work with any OHCI-1394
66 compliant card, however.
68 To compile this driver as a module, say M here: the
69 module will be called ohci1394.
74 config IEEE1394_VIDEO1394
75 tristate "OHCI-1394 Video support"
76 depends on IEEE1394 && IEEE1394_OHCI1394
78 This option enables video device usage for OHCI-1394 cards. Enable
79 this option only if you have an IEEE 1394 video device connected to
82 comment "SBP-2 support (for storage devices) requires SCSI"
83 depends on IEEE1394 && SCSI=n
86 tristate "SBP-2 support (Harddisks etc.)"
87 depends on IEEE1394 && SCSI
89 This option enables you to use SBP-2 devices connected to an IEEE
90 1394 bus. SBP-2 devices include storage devices like harddisks and
91 DVD drives, also some other FireWire devices like scanners.
93 You should also enable support for disks, CD-ROMs, etc. in the SCSI
94 configuration section.
96 config IEEE1394_SBP2_PHYS_DMA
97 bool "Enable replacement for physical DMA in SBP2"
98 depends on IEEE1394 && IEEE1394_SBP2 && EXPERIMENTAL && (X86_32 || PPC_32)
100 This builds sbp2 for use with non-OHCI host adapters which do not
101 support physical DMA or for when ohci1394 is run with phys_dma=0.
102 Physical DMA is data movement without assistance of the drivers'
103 interrupt handlers. This option includes the interrupt handlers
104 that are required in absence of this hardware feature.
106 This option is buggy and currently broken on some architectures.
109 config IEEE1394_ETH1394_ROM_ENTRY
114 config IEEE1394_ETH1394
115 tristate "IP over 1394"
116 depends on IEEE1394 && EXPERIMENTAL && INET
117 select IEEE1394_ETH1394_ROM_ENTRY
119 This driver implements a functional majority of RFC 2734: IPv4 over
120 1394. It will provide IP connectivity with implementations of RFC
121 2734 found on other operating systems. It will not communicate with
122 older versions of this driver found in stock kernels prior to 2.6.3.
123 This driver is still considered experimental. It does not yet support
124 MCAP, therefore multicast support is significantly limited.
126 The module is called eth1394 although it does not emulate Ethernet.
128 config IEEE1394_DV1394
129 tristate "OHCI-DV I/O support (deprecated)"
130 depends on IEEE1394 && IEEE1394_OHCI1394
132 The dv1394 driver is unsupported and may be removed from Linux in a
133 future release. Its functionality is now provided by raw1394 together
134 with libraries such as libiec61883.
136 config IEEE1394_RAWIO
137 tristate "Raw IEEE1394 I/O support"
140 This option adds support for the raw1394 device file which enables
141 direct communication of user programs with the IEEE 1394 bus and thus
142 with the attached peripherals. Almost all application programs which
143 access FireWire require this option.
145 To compile this driver as a module, say M here: the module will be