3 menu "IEEE 1394 (FireWire) support"
6 tristate "IEEE 1394 (FireWire) support"
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
36 config IEEE1394_OUI_DB
37 bool "OUI Database built-in"
40 If you say Y here, then an OUI list (vendor unique ID's) will be
41 compiled into the ieee1394 module. This doesn't really do much
42 except being able to display the vendor of a hardware node. The
43 downside is that it adds about 300k to the size of the module,
44 or kernel (depending on whether you compile ieee1394 as a
45 module, or static in the kernel).
47 This option is not needed for userspace programs like gscanbus
48 to show this information.
50 config IEEE1394_EXTRA_CONFIG_ROMS
51 bool "Build in extra config rom entries for certain functionality"
54 Some IEEE1394 functionality depends on extra config rom entries
55 being available in the host adapters CSR. These options will
56 allow you to choose which ones.
58 config IEEE1394_CONFIG_ROM_IP1394
60 depends on IEEE1394_EXTRA_CONFIG_ROMS && IEEE1394
62 Adds an entry for using IP-over-1394. If you want to use your
63 IEEE1394 bus as a network for IP systems (including interacting
64 with MacOSX and WinXP IP-over-1394), enable this option and the
67 comment "Device Drivers"
70 comment "Texas Instruments PCILynx requires I2C"
71 depends on IEEE1394 && I2C=n
73 config IEEE1394_PCILYNX
74 tristate "Texas Instruments PCILynx support"
75 depends on PCI && IEEE1394 && I2C
78 Say Y here if you have an IEEE-1394 controller with the Texas
79 Instruments PCILynx chip. Note: this driver is written for revision
80 2 of this chip and may not work with revision 0.
82 To compile this driver as a module, say M here: the
83 module will be called pcilynx.
85 # Non-maintained pcilynx options
86 # if [ "$CONFIG_IEEE1394_PCILYNX" != "n" ]; then
87 # bool ' Use PCILynx local RAM' CONFIG_IEEE1394_PCILYNX_LOCALRAM
88 # bool ' Support for non-IEEE1394 local ports' CONFIG_IEEE1394_PCILYNX_PORTS
90 config IEEE1394_OHCI1394
91 tristate "OHCI-1394 support"
92 depends on PCI && IEEE1394
94 Enable this driver if you have an IEEE 1394 controller based on the
95 OHCI-1394 specification. The current driver is only tested with OHCI
96 chipsets made by Texas Instruments and NEC. Most third-party vendors
97 use one of these chipsets. It should work with any OHCI-1394
98 compliant card, however.
100 To compile this driver as a module, say M here: the
101 module will be called ohci1394.
103 comment "Protocol Drivers"
106 config IEEE1394_VIDEO1394
107 tristate "OHCI-1394 Video support"
108 depends on IEEE1394 && IEEE1394_OHCI1394
110 This option enables video device usage for OHCI-1394 cards. Enable
111 this option only if you have an IEEE 1394 video device connected to
115 tristate "SBP-2 support (Harddisks etc.)"
116 depends on IEEE1394 && SCSI
118 This option enables you to use SBP-2 devices connected to your IEEE
119 1394 bus. SBP-2 devices include harddrives and DVD devices.
121 config IEEE1394_SBP2_PHYS_DMA
122 bool "Enable Phys DMA support for SBP2 (Debug)"
123 depends on IEEE1394 && IEEE1394_SBP2
125 config IEEE1394_ETH1394
126 tristate "Ethernet over 1394"
127 depends on IEEE1394 && EXPERIMENTAL && INET
128 select IEEE1394_CONFIG_ROM_IP1394
129 select IEEE1394_EXTRA_CONFIG_ROMS
131 This driver implements a functional majority of RFC 2734: IPv4 over
132 1394. It will provide IP connectivity with implementations of RFC
133 2734 found on other operating systems. It will not communicate with
134 older versions of this driver found in stock kernels prior to 2.6.3.
135 This driver is still considered experimental. It does not yet support
136 MCAP, therefore multicast support is significantly limited.
138 config IEEE1394_DV1394
139 tristate "OHCI-DV I/O support"
140 depends on IEEE1394 && IEEE1394_OHCI1394
142 This driver allows you to transmit and receive DV (digital video)
143 streams on an OHCI-1394 card using a simple frame-oriented
146 The user-space API for dv1394 is documented in dv1394.h.
148 To compile this driver as a module, say M here: the
149 module will be called dv1394.
151 config IEEE1394_RAWIO
152 tristate "Raw IEEE1394 I/O support"
155 Say Y here if you want support for the raw device. This is generally
156 a good idea, so you should say Y here. The raw device enables
157 direct communication of user programs with the IEEE 1394 bus and
158 thus with the attached peripherals.
160 To compile this driver as a module, say M here: the
161 module will be called raw1394.
164 tristate "IEC61883-1 Plug support"
167 This option enables the Connection Management Procedures
168 (IEC61883-1) driver, which implements input and output plugs.
170 To compile this driver as a module, say M here: the
171 module will be called cmp.
173 config IEEE1394_AMDTP
174 tristate "IEC61883-6 (Audio transmission) support"
175 depends on IEEE1394 && IEEE1394_OHCI1394 && IEEE1394_CMP
177 This option enables the Audio & Music Data Transmission Protocol
178 (IEC61883-6) driver, which implements audio transmission over
181 The userspace interface is documented in amdtp.h.
183 To compile this driver as a module, say M here: the
184 module will be called amdtp.