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_EXTRA_CONFIG_ROMS
38 bool "Build in extra config rom entries for certain functionality"
41 Some IEEE1394 functionality depends on extra config rom entries
42 being available in the host adapters CSR. These options will
43 allow you to choose which ones.
45 config IEEE1394_CONFIG_ROM_IP1394
47 depends on IEEE1394_EXTRA_CONFIG_ROMS && IEEE1394
49 Adds an entry for using IP-over-1394. If you want to use your
50 IEEE1394 bus as a network for IP systems (including interacting
51 with MacOSX and WinXP IP-over-1394), enable this option and the
54 comment "Device Drivers"
57 comment "Texas Instruments PCILynx requires I2C"
58 depends on IEEE1394 && I2C=n
60 config IEEE1394_PCILYNX
61 tristate "Texas Instruments PCILynx support"
62 depends on PCI && IEEE1394 && I2C
65 Say Y here if you have an IEEE-1394 controller with the Texas
66 Instruments PCILynx chip. Note: this driver is written for revision
67 2 of this chip and may not work with revision 0.
69 To compile this driver as a module, say M here: the
70 module will be called pcilynx.
72 config IEEE1394_OHCI1394
73 tristate "OHCI-1394 support"
74 depends on PCI && IEEE1394
76 Enable this driver if you have an IEEE 1394 controller based on the
77 OHCI-1394 specification. The current driver is only tested with OHCI
78 chipsets made by Texas Instruments and NEC. Most third-party vendors
79 use one of these chipsets. It should work with any OHCI-1394
80 compliant card, however.
82 To compile this driver as a module, say M here: the
83 module will be called ohci1394.
85 comment "Protocol Drivers"
88 config IEEE1394_VIDEO1394
89 tristate "OHCI-1394 Video support"
90 depends on IEEE1394 && IEEE1394_OHCI1394
92 This option enables video device usage for OHCI-1394 cards. Enable
93 this option only if you have an IEEE 1394 video device connected to
96 comment "SBP-2 support (for storage devices) requires SCSI"
97 depends on IEEE1394 && SCSI=n
100 tristate "SBP-2 support (Harddisks etc.)"
101 depends on IEEE1394 && SCSI
103 This option enables you to use SBP-2 devices connected to an IEEE
104 1394 bus. SBP-2 devices include storage devices like harddisks and
105 DVD drives, also some other FireWire devices like scanners.
107 You should also enable support for disks, CD-ROMs, etc. in the SCSI
108 configuration section.
110 config IEEE1394_SBP2_PHYS_DMA
111 bool "Enable replacement for physical DMA in SBP2"
112 depends on IEEE1394 && IEEE1394_SBP2 && EXPERIMENTAL && (X86_32 || PPC_32)
114 This builds sbp2 for use with non-OHCI host adapters which do not
115 support physical DMA or for when ohci1394 is run with phys_dma=0.
116 Physical DMA is data movement without assistance of the drivers'
117 interrupt handlers. This option includes the interrupt handlers
118 that are required in absence of this hardware feature.
120 This option is buggy and currently broken on some architectures.
123 config IEEE1394_ETH1394
124 tristate "Ethernet over 1394"
125 depends on IEEE1394 && EXPERIMENTAL && INET
126 select IEEE1394_CONFIG_ROM_IP1394
127 select IEEE1394_EXTRA_CONFIG_ROMS
129 This driver implements a functional majority of RFC 2734: IPv4 over
130 1394. It will provide IP connectivity with implementations of RFC
131 2734 found on other operating systems. It will not communicate with
132 older versions of this driver found in stock kernels prior to 2.6.3.
133 This driver is still considered experimental. It does not yet support
134 MCAP, therefore multicast support is significantly limited.
136 config IEEE1394_DV1394
137 tristate "OHCI-DV I/O support (deprecated)"
138 depends on IEEE1394 && IEEE1394_OHCI1394
140 The dv1394 driver is unsupported and may be removed from Linux in a
141 future release. Its functionality is now provided by raw1394 together
142 with libraries such as libiec61883.
144 config IEEE1394_RAWIO
145 tristate "Raw IEEE1394 I/O support"
148 Say Y here if you want support for the raw device. This is generally
149 a good idea, so you should say Y here. The raw device enables
150 direct communication of user programs with the IEEE 1394 bus and
151 thus with the attached peripherals.
153 To compile this driver as a module, say M here: the
154 module will be called raw1394.