3 menu "IEEE 1394 (FireWire) support"
6 tristate "IEEE 1394 (FireWire) support"
7 depends on PCI || BROKEN
9 IEEE 1394 describes a high performance serial bus, which is also
10 known as FireWire(tm) or i.Link(tm) and is used for connecting all
11 sorts of devices (most notably digital video cameras) to your
14 If you have FireWire hardware and want to use it, say Y here. This
15 is the core support only, you will also need to select a driver for
16 your IEEE 1394 adapter.
18 To compile this driver as a module, say M here: the
19 module will be called ieee1394.
21 comment "Subsystem Options"
24 config IEEE1394_VERBOSEDEBUG
25 bool "Excessive debugging output"
28 If you say Y here, you will get very verbose debugging logs from
29 the subsystem which includes a dump of the header of every sent
30 and received packet. This can amount to a high amount of data
31 collected in a very short time which is usually also saved to
32 disk by the system logging daemons.
34 Say Y if you really want or need the debugging output, everyone
37 config IEEE1394_OUI_DB
38 bool "OUI Database built-in"
41 If you say Y here, then an OUI list (vendor unique ID's) will be
42 compiled into the ieee1394 module. This doesn't really do much
43 except being able to display the vendor of a hardware node. The
44 downside is that it adds about 300k to the size of the module,
45 or kernel (depending on whether you compile ieee1394 as a
46 module, or static in the kernel).
48 This option is not needed for userspace programs like gscanbus
49 to show this information.
51 config IEEE1394_EXTRA_CONFIG_ROMS
52 bool "Build in extra config rom entries for certain functionality"
55 Some IEEE1394 functionality depends on extra config rom entries
56 being available in the host adapters CSR. These options will
57 allow you to choose which ones.
59 config IEEE1394_CONFIG_ROM_IP1394
61 depends on IEEE1394_EXTRA_CONFIG_ROMS && IEEE1394
63 Adds an entry for using IP-over-1394. If you want to use your
64 IEEE1394 bus as a network for IP systems (including interacting
65 with MacOSX and WinXP IP-over-1394), enable this option and the
68 comment "Device Drivers"
71 comment "Texas Instruments PCILynx requires I2C"
72 depends on IEEE1394 && I2C=n
74 config IEEE1394_PCILYNX
75 tristate "Texas Instruments PCILynx support"
76 depends on PCI && IEEE1394 && I2C
79 Say Y here if you have an IEEE-1394 controller with the Texas
80 Instruments PCILynx chip. Note: this driver is written for revision
81 2 of this chip and may not work with revision 0.
83 To compile this driver as a module, say M here: the
84 module will be called pcilynx.
86 # Non-maintained pcilynx options
87 # if [ "$CONFIG_IEEE1394_PCILYNX" != "n" ]; then
88 # bool ' Use PCILynx local RAM' CONFIG_IEEE1394_PCILYNX_LOCALRAM
89 # bool ' Support for non-IEEE1394 local ports' CONFIG_IEEE1394_PCILYNX_PORTS
91 config IEEE1394_OHCI1394
92 tristate "OHCI-1394 support"
93 depends on PCI && IEEE1394
95 Enable this driver if you have an IEEE 1394 controller based on the
96 OHCI-1394 specification. The current driver is only tested with OHCI
97 chipsets made by Texas Instruments and NEC. Most third-party vendors
98 use one of these chipsets. It should work with any OHCI-1394
99 compliant card, however.
101 To compile this driver as a module, say M here: the
102 module will be called ohci1394.
104 comment "Protocol Drivers"
107 config IEEE1394_VIDEO1394
108 tristate "OHCI-1394 Video support"
109 depends on IEEE1394 && IEEE1394_OHCI1394
111 This option enables video device usage for OHCI-1394 cards. Enable
112 this option only if you have an IEEE 1394 video device connected to
116 tristate "SBP-2 support (Harddisks etc.)"
117 depends on IEEE1394 && SCSI && (PCI || BROKEN)
119 This option enables you to use SBP-2 devices connected to your IEEE
120 1394 bus. SBP-2 devices include harddrives and DVD devices.
122 config IEEE1394_SBP2_PHYS_DMA
123 bool "Enable Phys DMA support for SBP2 (Debug)"
124 depends on IEEE1394 && IEEE1394_SBP2
126 config IEEE1394_ETH1394
127 tristate "Ethernet over 1394"
128 depends on IEEE1394 && EXPERIMENTAL && INET
129 select IEEE1394_CONFIG_ROM_IP1394
130 select IEEE1394_EXTRA_CONFIG_ROMS
132 This driver implements a functional majority of RFC 2734: IPv4 over
133 1394. It will provide IP connectivity with implementations of RFC
134 2734 found on other operating systems. It will not communicate with
135 older versions of this driver found in stock kernels prior to 2.6.3.
136 This driver is still considered experimental. It does not yet support
137 MCAP, therefore multicast support is significantly limited.
139 config IEEE1394_DV1394
140 tristate "OHCI-DV I/O support"
141 depends on IEEE1394 && IEEE1394_OHCI1394
143 This driver allows you to transmit and receive DV (digital video)
144 streams on an OHCI-1394 card using a simple frame-oriented
147 The user-space API for dv1394 is documented in dv1394.h.
149 To compile this driver as a module, say M here: the
150 module will be called dv1394.
152 config IEEE1394_RAWIO
153 tristate "Raw IEEE1394 I/O support"
156 Say Y here if you want support for the raw device. This is generally
157 a good idea, so you should say Y here. The raw device enables
158 direct communication of user programs with the IEEE 1394 bus and
159 thus with the attached peripherals.
161 To compile this driver as a module, say M here: the
162 module will be called raw1394.
165 tristate "IEC61883-1 Plug support"
168 This option enables the Connection Management Procedures
169 (IEC61883-1) driver, which implements input and output plugs.
171 To compile this driver as a module, say M here: the
172 module will be called cmp.
174 config IEEE1394_AMDTP
175 tristate "IEC61883-6 (Audio transmission) support"
176 depends on IEEE1394 && IEEE1394_OHCI1394 && IEEE1394_CMP
178 This option enables the Audio & Music Data Transmission Protocol
179 (IEC61883-6) driver, which implements audio transmission over
182 The userspace interface is documented in amdtp.h.
184 To compile this driver as a module, say M here: the
185 module will be called amdtp.