3 menu "IEEE 1394 (FireWire) support"
5 source "drivers/firewire/Kconfig"
8 tristate "IEEE 1394 (FireWire) support"
9 depends on PCI || BROKEN
12 IEEE 1394 describes a high performance serial bus, which is also
13 known as FireWire(tm) or i.Link(tm) and is used for connecting all
14 sorts of devices (most notably digital video cameras) to your
17 If you have FireWire hardware and want to use it, say Y here. This
18 is the core support only, you will also need to select a driver for
19 your IEEE 1394 adapter.
21 To compile this driver as a module, say M here: the
22 module will be called ieee1394.
24 comment "Subsystem Options"
27 config IEEE1394_VERBOSEDEBUG
28 bool "Excessive debugging output"
31 If you say Y here, you will get very verbose debugging logs from
32 the subsystem which includes a dump of the header of every sent
33 and received packet. This can amount to a high amount of data
34 collected in a very short time which is usually also saved to
35 disk by the system logging daemons.
37 Say Y if you really want or need the debugging output, everyone
40 config IEEE1394_EXTRA_CONFIG_ROMS
41 bool "Build in extra config rom entries for certain functionality"
44 Some IEEE1394 functionality depends on extra config rom entries
45 being available in the host adapters CSR. These options will
46 allow you to choose which ones.
48 config IEEE1394_CONFIG_ROM_IP1394
50 depends on IEEE1394_EXTRA_CONFIG_ROMS && IEEE1394
52 Adds an entry for using IP-over-1394. If you want to use your
53 IEEE1394 bus as a network for IP systems (including interacting
54 with MacOSX and WinXP IP-over-1394), enable this option and the
57 comment "Device Drivers"
60 comment "Texas Instruments PCILynx requires I2C"
61 depends on IEEE1394 && I2C=n
63 config IEEE1394_PCILYNX
64 tristate "Texas Instruments PCILynx support"
65 depends on PCI && IEEE1394 && I2C
68 Say Y here if you have an IEEE-1394 controller with the Texas
69 Instruments PCILynx chip. Note: this driver is written for revision
70 2 of this chip and may not work with revision 0.
72 To compile this driver as a module, say M here: the
73 module will be called pcilynx.
75 config IEEE1394_OHCI1394
76 tristate "OHCI-1394 support"
77 depends on PCI && IEEE1394
79 Enable this driver if you have an IEEE 1394 controller based on the
80 OHCI-1394 specification. The current driver is only tested with OHCI
81 chipsets made by Texas Instruments and NEC. Most third-party vendors
82 use one of these chipsets. It should work with any OHCI-1394
83 compliant card, however.
85 To compile this driver as a module, say M here: the
86 module will be called ohci1394.
88 comment "Protocol Drivers"
91 config IEEE1394_VIDEO1394
92 tristate "OHCI-1394 Video support"
93 depends on IEEE1394 && IEEE1394_OHCI1394
95 This option enables video device usage for OHCI-1394 cards. Enable
96 this option only if you have an IEEE 1394 video device connected to
99 comment "SBP-2 support (for storage devices) requires SCSI"
100 depends on IEEE1394 && SCSI=n
103 tristate "SBP-2 support (Harddisks etc.)"
104 depends on IEEE1394 && SCSI
106 This option enables you to use SBP-2 devices connected to an IEEE
107 1394 bus. SBP-2 devices include storage devices like harddisks and
108 DVD drives, also some other FireWire devices like scanners.
110 You should also enable support for disks, CD-ROMs, etc. in the SCSI
111 configuration section.
113 config IEEE1394_SBP2_PHYS_DMA
114 bool "Enable replacement for physical DMA in SBP2"
115 depends on IEEE1394 && IEEE1394_SBP2 && EXPERIMENTAL && (X86_32 || PPC_32)
117 This builds sbp2 for use with non-OHCI host adapters which do not
118 support physical DMA or for when ohci1394 is run with phys_dma=0.
119 Physical DMA is data movement without assistance of the drivers'
120 interrupt handlers. This option includes the interrupt handlers
121 that are required in absence of this hardware feature.
123 This option is buggy and currently broken on some architectures.
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 (deprecated)"
141 depends on IEEE1394 && IEEE1394_OHCI1394
143 The dv1394 driver will be removed from Linux in a future release.
144 Its functionality is now provided by raw1394 together with libraries
147 config IEEE1394_RAWIO
148 tristate "Raw IEEE1394 I/O support"
151 Say Y here if you want support for the raw device. This is generally
152 a good idea, so you should say Y here. The raw device enables
153 direct communication of user programs with the IEEE 1394 bus and
154 thus with the attached peripherals.
156 To compile this driver as a module, say M here: the
157 module will be called raw1394.