diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2009-12-31 15:01:24 -0500 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-12-31 15:01:24 -0500 |
commit | b7bfb2a7a9296871a5e45c35a2cdc6a174995aa7 (patch) | |
tree | 7e7bc2b636b2bd906455a45a9cae648f957a27fc /drivers/ieee1394/Kconfig | |
parent | 5b889bf237fca383b5807ad69fde3ad1e2287e42 (diff) | |
parent | 5d7db0499e5bb13381a7fbfdd0d913b966545e75 (diff) |
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6
* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6:
firewire, ieee1394: update Kconfig help
firewire, ieee1394: update MAINTAINERS entries
firewire: ohci: always use packet-per-buffer mode for isochronous reception
firewire: cdev: fix another memory leak in an error path
firewire: fix use of multiple AV/C devices, allow multiple FCP listeners
Comments from Stefan:
Distributors who still ship the old stack (ieee1394, ohci1394,
raw1394, sbp2, eth1394 and more) should now switch to the new one
(firewire-core, firewire-ohci, firewire-sbp2, firewire-net). In the
first iteration, those distributors might want to ship the old stack
also (but blacklisted) as a fallback for their users if unforeseen
problems with the newer replacement drivers are encountered.
The older FireWire stack contains several known problems which are
not going to be fixed; instead, those issues are addressed by the new
stack. An incomplete list of these issues is kept in bugzilla:
http://bugzilla.kernel.org/show_bug.cgi?id=10046
We have a guide on migration from the older to the newer stack:
http://ieee1394.wiki.kernel.org/index.php/Juju_Migration
Diffstat (limited to 'drivers/ieee1394/Kconfig')
-rw-r--r-- | drivers/ieee1394/Kconfig | 59 |
1 files changed, 42 insertions, 17 deletions
diff --git a/drivers/ieee1394/Kconfig b/drivers/ieee1394/Kconfig index f102fcc7e52a..e02096cf7d95 100644 --- a/drivers/ieee1394/Kconfig +++ b/drivers/ieee1394/Kconfig | |||
@@ -1,8 +1,3 @@ | |||
1 | menu "IEEE 1394 (FireWire) support" | ||
2 | depends on PCI || BROKEN | ||
3 | |||
4 | source "drivers/firewire/Kconfig" | ||
5 | |||
6 | config IEEE1394 | 1 | config IEEE1394 |
7 | tristate "Legacy alternative FireWire driver stack" | 2 | tristate "Legacy alternative FireWire driver stack" |
8 | depends on PCI || BROKEN | 3 | depends on PCI || BROKEN |
@@ -16,8 +11,13 @@ config IEEE1394 | |||
16 | is the core support only, you will also need to select a driver for | 11 | is the core support only, you will also need to select a driver for |
17 | your IEEE 1394 adapter. | 12 | your IEEE 1394 adapter. |
18 | 13 | ||
19 | To compile this driver as a module, say M here: the | 14 | To compile this driver as a module, say M here: the module will be |
20 | module will be called ieee1394. | 15 | called ieee1394. |
16 | |||
17 | NOTE: | ||
18 | ieee1394 is superseded by the newer firewire-core driver. See | ||
19 | http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for | ||
20 | further information on how to switch to the new FireWire drivers. | ||
21 | 21 | ||
22 | config IEEE1394_OHCI1394 | 22 | config IEEE1394_OHCI1394 |
23 | tristate "OHCI-1394 controllers" | 23 | tristate "OHCI-1394 controllers" |
@@ -29,19 +29,23 @@ config IEEE1394_OHCI1394 | |||
29 | use one of these chipsets. It should work with any OHCI-1394 | 29 | use one of these chipsets. It should work with any OHCI-1394 |
30 | compliant card, however. | 30 | compliant card, however. |
31 | 31 | ||
32 | To compile this driver as a module, say M here: the | 32 | To compile this driver as a module, say M here: the module will be |
33 | module will be called ohci1394. | 33 | called ohci1394. |
34 | 34 | ||
35 | NOTE: | 35 | NOTE: |
36 | ohci1394 is superseded by the newer firewire-ohci driver. See | ||
37 | http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for | ||
38 | further information on how to switch to the new FireWire drivers. | ||
39 | |||
36 | If you want to install firewire-ohci and ohci1394 together, you | 40 | If you want to install firewire-ohci and ohci1394 together, you |
37 | should configure them only as modules and blacklist the driver(s) | 41 | should configure them only as modules and blacklist the driver(s) |
38 | which you don't want to have auto-loaded. Add either | 42 | which you don't want to have auto-loaded. Add either |
39 | 43 | ||
40 | blacklist firewire-ohci | ||
41 | or | ||
42 | blacklist ohci1394 | 44 | blacklist ohci1394 |
43 | blacklist video1394 | 45 | blacklist video1394 |
44 | blacklist dv1394 | 46 | blacklist dv1394 |
47 | or | ||
48 | blacklist firewire-ohci | ||
45 | 49 | ||
46 | to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf | 50 | to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf |
47 | depending on your distribution. | 51 | depending on your distribution. |
@@ -58,8 +62,8 @@ config IEEE1394_PCILYNX | |||
58 | Instruments PCILynx chip. Note: this driver is written for revision | 62 | Instruments PCILynx chip. Note: this driver is written for revision |
59 | 2 of this chip and may not work with revision 0. | 63 | 2 of this chip and may not work with revision 0. |
60 | 64 | ||
61 | To compile this driver as a module, say M here: the | 65 | To compile this driver as a module, say M here: the module will be |
62 | module will be called pcilynx. | 66 | called pcilynx. |
63 | 67 | ||
64 | Only some old and now very rare PCI and CardBus cards and | 68 | Only some old and now very rare PCI and CardBus cards and |
65 | PowerMacs G3 B&W contain the PCILynx controller. Therefore | 69 | PowerMacs G3 B&W contain the PCILynx controller. Therefore |
@@ -79,6 +83,14 @@ config IEEE1394_SBP2 | |||
79 | You should also enable support for disks, CD-ROMs, etc. in the SCSI | 83 | You should also enable support for disks, CD-ROMs, etc. in the SCSI |
80 | configuration section. | 84 | configuration section. |
81 | 85 | ||
86 | To compile this driver as a module, say M here: the module will be | ||
87 | called sbp2. | ||
88 | |||
89 | NOTE: | ||
90 | sbp2 is superseded by the newer firewire-sbp2 driver. See | ||
91 | http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for | ||
92 | further information on how to switch to the new FireWire drivers. | ||
93 | |||
82 | config IEEE1394_SBP2_PHYS_DMA | 94 | config IEEE1394_SBP2_PHYS_DMA |
83 | bool "Enable replacement for physical DMA in SBP2" | 95 | bool "Enable replacement for physical DMA in SBP2" |
84 | depends on IEEE1394_SBP2 && VIRT_TO_BUS && EXPERIMENTAL | 96 | depends on IEEE1394_SBP2 && VIRT_TO_BUS && EXPERIMENTAL |
@@ -111,6 +123,11 @@ config IEEE1394_ETH1394 | |||
111 | 123 | ||
112 | The module is called eth1394 although it does not emulate Ethernet. | 124 | The module is called eth1394 although it does not emulate Ethernet. |
113 | 125 | ||
126 | NOTE: | ||
127 | eth1394 is superseded by the newer firewire-net driver. See | ||
128 | http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for | ||
129 | further information on how to switch to the new FireWire drivers. | ||
130 | |||
114 | config IEEE1394_RAWIO | 131 | config IEEE1394_RAWIO |
115 | tristate "raw1394 userspace interface" | 132 | tristate "raw1394 userspace interface" |
116 | depends on IEEE1394 | 133 | depends on IEEE1394 |
@@ -123,6 +140,11 @@ config IEEE1394_RAWIO | |||
123 | To compile this driver as a module, say M here: the module will be | 140 | To compile this driver as a module, say M here: the module will be |
124 | called raw1394. | 141 | called raw1394. |
125 | 142 | ||
143 | NOTE: | ||
144 | raw1394 is superseded by the newer firewire-core driver. See | ||
145 | http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for | ||
146 | further information on how to switch to the new FireWire drivers. | ||
147 | |||
126 | config IEEE1394_VIDEO1394 | 148 | config IEEE1394_VIDEO1394 |
127 | tristate "video1394 userspace interface" | 149 | tristate "video1394 userspace interface" |
128 | depends on IEEE1394 && IEEE1394_OHCI1394 | 150 | depends on IEEE1394 && IEEE1394_OHCI1394 |
@@ -136,13 +158,18 @@ config IEEE1394_VIDEO1394 | |||
136 | To compile this driver as a module, say M here: the module will be | 158 | To compile this driver as a module, say M here: the module will be |
137 | called video1394. | 159 | called video1394. |
138 | 160 | ||
161 | NOTE: | ||
162 | video1394 is superseded by the newer firewire-core driver. See | ||
163 | http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for | ||
164 | further information on how to switch to the new FireWire drivers. | ||
165 | |||
139 | config IEEE1394_DV1394 | 166 | config IEEE1394_DV1394 |
140 | tristate "dv1394 userspace interface (deprecated)" | 167 | tristate "dv1394 userspace interface (deprecated)" |
141 | depends on IEEE1394 && IEEE1394_OHCI1394 | 168 | depends on IEEE1394 && IEEE1394_OHCI1394 |
142 | help | 169 | help |
143 | The dv1394 driver is unsupported and may be removed from Linux in a | 170 | The dv1394 driver is unsupported and may be removed from Linux in a |
144 | future release. Its functionality is now provided by raw1394 together | 171 | future release. Its functionality is now provided by either |
145 | with libraries such as libiec61883. | 172 | raw1394 or firewire-core together with libraries such as libiec61883. |
146 | 173 | ||
147 | config IEEE1394_VERBOSEDEBUG | 174 | config IEEE1394_VERBOSEDEBUG |
148 | bool "Excessive debugging output" | 175 | bool "Excessive debugging output" |
@@ -153,5 +180,3 @@ config IEEE1394_VERBOSEDEBUG | |||
153 | will quickly result in large amounts of data sent to the system log. | 180 | will quickly result in large amounts of data sent to the system log. |
154 | 181 | ||
155 | Say Y if you really need the debugging output. Everyone else says N. | 182 | Say Y if you really need the debugging output. Everyone else says N. |
156 | |||
157 | endmenu | ||