blob: 5c0b522ae0778770c1f223c4cb7b868f33d05437 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001# -*- shell-script -*-
2
3menu "IEEE 1394 (FireWire) support"
4
5config IEEE1394
6 tristate "IEEE 1394 (FireWire) support"
Stefan Richter09a9a452006-06-25 05:46:44 -07007 depends on PCI || BROKEN
Linus Torvalds1da177e2005-04-16 15:20:36 -07008 help
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
12 computer.
13
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.
17
18 To compile this driver as a module, say M here: the
19 module will be called ieee1394.
20
21comment "Subsystem Options"
22 depends on IEEE1394
23
24config IEEE1394_VERBOSEDEBUG
25 bool "Excessive debugging output"
26 depends on IEEE1394
27 help
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.
33
34 Say Y if you really want or need the debugging output, everyone
35 else says N.
36
Linus Torvalds1da177e2005-04-16 15:20:36 -070037comment "Device Drivers"
38 depends on IEEE1394
39
40comment "Texas Instruments PCILynx requires I2C"
41 depends on IEEE1394 && I2C=n
42
43config IEEE1394_PCILYNX
44 tristate "Texas Instruments PCILynx support"
45 depends on PCI && IEEE1394 && I2C
46 select I2C_ALGOBIT
47 help
48 Say Y here if you have an IEEE-1394 controller with the Texas
49 Instruments PCILynx chip. Note: this driver is written for revision
50 2 of this chip and may not work with revision 0.
51
52 To compile this driver as a module, say M here: the
53 module will be called pcilynx.
54
Linus Torvalds1da177e2005-04-16 15:20:36 -070055config IEEE1394_OHCI1394
56 tristate "OHCI-1394 support"
57 depends on PCI && IEEE1394
58 help
59 Enable this driver if you have an IEEE 1394 controller based on the
60 OHCI-1394 specification. The current driver is only tested with OHCI
61 chipsets made by Texas Instruments and NEC. Most third-party vendors
62 use one of these chipsets. It should work with any OHCI-1394
63 compliant card, however.
64
65 To compile this driver as a module, say M here: the
66 module will be called ohci1394.
67
68comment "Protocol Drivers"
69 depends on IEEE1394
70
71config IEEE1394_VIDEO1394
72 tristate "OHCI-1394 Video support"
73 depends on IEEE1394 && IEEE1394_OHCI1394
74 help
75 This option enables video device usage for OHCI-1394 cards. Enable
76 this option only if you have an IEEE 1394 video device connected to
77 an OHCI-1394 card.
78
Stefan Richterb8092892006-08-30 18:22:00 +020079comment "SBP-2 support (for storage devices) requires SCSI"
80 depends on IEEE1394 && SCSI=n
81
Linus Torvalds1da177e2005-04-16 15:20:36 -070082config IEEE1394_SBP2
83 tristate "SBP-2 support (Harddisks etc.)"
Stefan Richter9b7d9c02006-11-22 21:44:34 +010084 depends on IEEE1394 && SCSI
Linus Torvalds1da177e2005-04-16 15:20:36 -070085 help
Stefan Richterb8092892006-08-30 18:22:00 +020086 This option enables you to use SBP-2 devices connected to an IEEE
87 1394 bus. SBP-2 devices include storage devices like harddisks and
88 DVD drives, also some other FireWire devices like scanners.
89
90 You should also enable support for disks, CD-ROMs, etc. in the SCSI
91 configuration section.
Linus Torvalds1da177e2005-04-16 15:20:36 -070092
93config IEEE1394_SBP2_PHYS_DMA
Ben Collinsbccbccd2006-06-12 18:14:36 -040094 bool "Enable replacement for physical DMA in SBP2"
Ben Collinsdd082c62006-06-12 18:15:40 -040095 depends on IEEE1394 && IEEE1394_SBP2 && EXPERIMENTAL && (X86_32 || PPC_32)
Ben Collinsbccbccd2006-06-12 18:14:36 -040096 help
97 This builds sbp2 for use with non-OHCI host adapters which do not
98 support physical DMA or for when ohci1394 is run with phys_dma=0.
Matt LaPlante09509602006-10-03 22:31:37 +020099 Physical DMA is data movement without assistance of the drivers'
Ben Collinsbccbccd2006-06-12 18:14:36 -0400100 interrupt handlers. This option includes the interrupt handlers
101 that are required in absence of this hardware feature.
102
103 This option is buggy and currently broken on some architectures.
104 If unsure, say N.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700105
Stefan Richter70093cf2007-03-27 01:36:50 +0200106config IEEE1394_ETH1394_ROM_ENTRY
107 depends on IEEE1394
108 bool
109 default n
110
Linus Torvalds1da177e2005-04-16 15:20:36 -0700111config IEEE1394_ETH1394
Stefan Richter70093cf2007-03-27 01:36:50 +0200112 tristate "IP over 1394"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113 depends on IEEE1394 && EXPERIMENTAL && INET
Stefan Richter70093cf2007-03-27 01:36:50 +0200114 select IEEE1394_ETH1394_ROM_ENTRY
Linus Torvalds1da177e2005-04-16 15:20:36 -0700115 help
116 This driver implements a functional majority of RFC 2734: IPv4 over
117 1394. It will provide IP connectivity with implementations of RFC
118 2734 found on other operating systems. It will not communicate with
119 older versions of this driver found in stock kernels prior to 2.6.3.
120 This driver is still considered experimental. It does not yet support
121 MCAP, therefore multicast support is significantly limited.
122
Stefan Richter70093cf2007-03-27 01:36:50 +0200123 The module is called eth1394 although it does not emulate Ethernet.
124
Linus Torvalds1da177e2005-04-16 15:20:36 -0700125config IEEE1394_DV1394
Stefan Richter861646f2006-11-20 00:07:26 +0100126 tristate "OHCI-DV I/O support (deprecated)"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700127 depends on IEEE1394 && IEEE1394_OHCI1394
128 help
Stefan Richter199c1162007-03-22 00:40:06 +0100129 The dv1394 driver is unsupported and may be removed from Linux in a
130 future release. Its functionality is now provided by raw1394 together
131 with libraries such as libiec61883.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700132
133config IEEE1394_RAWIO
134 tristate "Raw IEEE1394 I/O support"
135 depends on IEEE1394
136 help
137 Say Y here if you want support for the raw device. This is generally
138 a good idea, so you should say Y here. The raw device enables
139 direct communication of user programs with the IEEE 1394 bus and
140 thus with the attached peripherals.
141
142 To compile this driver as a module, say M here: the
143 module will be called raw1394.
144
Linus Torvalds1da177e2005-04-16 15:20:36 -0700145endmenu