3 menu "IEEE 1394 (FireWire) support"
6 tristate "IEEE 1394 (FireWire) support"
7 depends on PCI || BROKEN
10 IEEE 1394 describes a high performance serial bus, which is also
11 known as FireWire(tm) or i.Link(tm) and is used for connecting all
12 sorts of devices (most notably digital video cameras) to your
15 If you have FireWire hardware and want to use it, say Y here. This
16 is the core support only, you will also need to select a driver for
17 your IEEE 1394 adapter.
19 To compile this driver as a module, say M here: the
20 module will be called ieee1394.
22 comment "Subsystem Options"
25 config IEEE1394_VERBOSEDEBUG
26 bool "Excessive debugging output"
29 If you say Y here, you will get very verbose debugging logs from
30 the subsystem which includes a dump of the header of every sent
31 and received packet. This can amount to a high amount of data
32 collected in a very short time which is usually also saved to
33 disk by the system logging daemons.
35 Say Y if you really want or need the debugging output, everyone
38 config IEEE1394_EXTRA_CONFIG_ROMS
39 bool "Build in extra config rom entries for certain functionality"
42 Some IEEE1394 functionality depends on extra config rom entries
43 being available in the host adapters CSR. These options will
44 allow you to choose which ones.
46 config IEEE1394_CONFIG_ROM_IP1394
48 depends on IEEE1394_EXTRA_CONFIG_ROMS && IEEE1394
50 Adds an entry for using IP-over-1394. If you want to use your
51 IEEE1394 bus as a network for IP systems (including interacting
52 with MacOSX and WinXP IP-over-1394), enable this option and the
55 comment "Device Drivers"
58 comment "Texas Instruments PCILynx requires I2C"
59 depends on IEEE1394 && I2C=n
61 config IEEE1394_PCILYNX
62 tristate "Texas Instruments PCILynx support"
63 depends on PCI && IEEE1394 && I2C
66 Say Y here if you have an IEEE-1394 controller with the Texas
67 Instruments PCILynx chip. Note: this driver is written for revision
68 2 of this chip and may not work with revision 0.
70 To compile this driver as a module, say M here: the
71 module will be called pcilynx.
73 config IEEE1394_OHCI1394
74 tristate "OHCI-1394 support"
75 depends on PCI && IEEE1394
77 Enable this driver if you have an IEEE 1394 controller based on the
78 OHCI-1394 specification. The current driver is only tested with OHCI
79 chipsets made by Texas Instruments and NEC. Most third-party vendors
80 use one of these chipsets. It should work with any OHCI-1394
81 compliant card, however.
83 To compile this driver as a module, say M here: the
84 module will be called ohci1394.
86 comment "Protocol Drivers"
89 config IEEE1394_VIDEO1394
90 tristate "OHCI-1394 Video support"
91 depends on IEEE1394 && IEEE1394_OHCI1394
93 This option enables video device usage for OHCI-1394 cards. Enable
94 this option only if you have an IEEE 1394 video device connected to
97 comment "SBP-2 support (for storage devices) requires SCSI"
98 depends on IEEE1394 && SCSI=n
101 tristate "SBP-2 support (Harddisks etc.)"
102 depends on IEEE1394 && SCSI
104 This option enables you to use SBP-2 devices connected to an IEEE
105 1394 bus. SBP-2 devices include storage devices like harddisks and
106 DVD drives, also some other FireWire devices like scanners.
108 You should also enable support for disks, CD-ROMs, etc. in the SCSI
109 configuration section.
111 config IEEE1394_SBP2_PHYS_DMA
112 bool "Enable replacement for physical DMA in SBP2"
113 depends on IEEE1394 && IEEE1394_SBP2 && EXPERIMENTAL && (X86_32 || PPC_32)
115 This builds sbp2 for use with non-OHCI host adapters which do not
116 support physical DMA or for when ohci1394 is run with phys_dma=0.
117 Physical DMA is data movement without assistance of the drivers'
118 interrupt handlers. This option includes the interrupt handlers
119 that are required in absence of this hardware feature.
121 This option is buggy and currently broken on some architectures.
124 config IEEE1394_ETH1394
125 tristate "Ethernet over 1394"
126 depends on IEEE1394 && EXPERIMENTAL && INET
127 select IEEE1394_CONFIG_ROM_IP1394
128 select IEEE1394_EXTRA_CONFIG_ROMS
130 This driver implements a functional majority of RFC 2734: IPv4 over
131 1394. It will provide IP connectivity with implementations of RFC
132 2734 found on other operating systems. It will not communicate with
133 older versions of this driver found in stock kernels prior to 2.6.3.
134 This driver is still considered experimental. It does not yet support
135 MCAP, therefore multicast support is significantly limited.
137 config IEEE1394_DV1394
138 tristate "OHCI-DV I/O support (deprecated)"
139 depends on IEEE1394 && IEEE1394_OHCI1394
141 The dv1394 driver is unsupported and may be removed from Linux in a
142 future release. Its functionality is now provided by raw1394 together
143 with libraries such as libiec61883.
145 config IEEE1394_RAWIO
146 tristate "Raw IEEE1394 I/O support"
149 Say Y here if you want support for the raw device. This is generally
150 a good idea, so you should say Y here. The raw device enables
151 direct communication of user programs with the IEEE 1394 bus and
152 thus with the attached peripherals.
154 To compile this driver as a module, say M here: the
155 module will be called raw1394.