1 files changed, 0 insertions, 182 deletions
diff --git a/drivers/ieee1394/Kconfig b/drivers/ieee1394/Kconfig
deleted file mode 100644
index e02096cf7d95..000000000000
--- a/drivers/ieee1394/Kconfig
+++ /dev/null
@@ -1,182 +0,0 @@
-config IEEE1394
-        tristate "Legacy alternative FireWire driver stack"
-        depends on PCI || BROKEN
-        help
-          IEEE 1394 describes a high performance serial bus, which is also
-          known as FireWire(tm) or i.Link(tm) and is used for connecting all
-          sorts of devices (most notably digital video cameras) to your
-          computer.
-          If you have FireWire hardware and want to use it, say Y here.  This
-          is the core support only, you will also need to select a driver for
-          your IEEE 1394 adapter.
-          To compile this driver as a module, say M here: the module will be
-          called ieee1394.
-          NOTE:
-          ieee1394 is superseded by the newer firewire-core driver.  See
-          http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for
-          further information on how to switch to the new FireWire drivers.
-config IEEE1394_OHCI1394
-        tristate "OHCI-1394 controllers"
-        depends on PCI && IEEE1394
-        help
-          Enable this driver if you have an IEEE 1394 controller based on the
-          OHCI-1394 specification. The current driver is only tested with OHCI
-          chipsets made by Texas Instruments and NEC. Most third-party vendors
-          use one of these chipsets.  It should work with any OHCI-1394
-          compliant card, however.
-          To compile this driver as a module, say M here: the module will be
-          called ohci1394.
-          NOTE:
-          ohci1394 is superseded by the newer firewire-ohci driver.  See
-          http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for
-          further information on how to switch to the new FireWire drivers.
-          If you want to install firewire-ohci and ohci1394 together, you
-          should configure them only as modules and blacklist the driver(s)
-          which you don't want to have auto-loaded.  Add either
-              blacklist ohci1394
-              blacklist video1394
-              blacklist dv1394
-          or
-              blacklist firewire-ohci
-          to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf
-          depending on your distribution.
-comment "PCILynx controller requires I2C"
-        depends on IEEE1394 && I2C=n
-config IEEE1394_PCILYNX
-        tristate "PCILynx controller"
-        depends on PCI && IEEE1394 && I2C
-        select I2C_ALGOBIT
-        help
-          Say Y here if you have an IEEE-1394 controller with the Texas
-          Instruments PCILynx chip.  Note: this driver is written for revision
-          2 of this chip and may not work with revision 0.
-          To compile this driver as a module, say M here: the module will be
-          called pcilynx.
-          Only some old and now very rare PCI and CardBus cards and
-          PowerMacs G3 B&W contain the PCILynx controller.  Therefore
-          almost everybody can say N here.
-comment "SBP-2 support (for storage devices) requires SCSI"
-        depends on IEEE1394 && SCSI=n
-config IEEE1394_SBP2
-        tristate "Storage devices (SBP-2 protocol)"
-        depends on IEEE1394 && SCSI
-        help
-          This option enables you to use SBP-2 devices connected to an IEEE
-          1394 bus.  SBP-2 devices include storage devices like harddisks and
-          DVD drives, also some other FireWire devices like scanners.
-          You should also enable support for disks, CD-ROMs, etc. in the SCSI
-          configuration section.
-          To compile this driver as a module, say M here: the module will be
-          called sbp2.
-          NOTE:
-          sbp2 is superseded by the newer firewire-sbp2 driver. See
-          http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for
-          further information on how to switch to the new FireWire drivers.
-config IEEE1394_SBP2_PHYS_DMA
-        bool "Enable replacement for physical DMA in SBP2"
-        depends on IEEE1394_SBP2 && VIRT_TO_BUS && EXPERIMENTAL
-        help
-          This builds sbp2 for use with non-OHCI host adapters which do not
-          support physical DMA or for when ohci1394 is run with phys_dma=0.
-          Physical DMA is data movement without assistance of the drivers'
-          interrupt handlers.  This option includes the interrupt handlers
-          that are required in absence of this hardware feature.
-          This option is buggy and currently broken on some architectures.
-          If unsure, say N.
-config IEEE1394_ETH1394_ROM_ENTRY
-        depends on IEEE1394
-        bool
-        default n
-config IEEE1394_ETH1394
-        tristate "IP networking over 1394 (experimental)"
-        depends on IEEE1394 && EXPERIMENTAL && INET
-        select IEEE1394_ETH1394_ROM_ENTRY
-        help
-          This driver implements a functional majority of RFC 2734: IPv4 over
-          1394.  It will provide IP connectivity with implementations of RFC
-          2734 found on other operating systems.  It will not communicate with
-          older versions of this driver found in stock kernels prior to 2.6.3.
-          This driver is still considered experimental.  It does not yet support
-          MCAP, therefore multicast support is significantly limited.
-          The module is called eth1394 although it does not emulate Ethernet.
-          NOTE:
-          eth1394 is superseded by the newer firewire-net driver. See
-          http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for
-          further information on how to switch to the new FireWire drivers.
-config IEEE1394_RAWIO
-        tristate "raw1394 userspace interface"
-        depends on IEEE1394
-        help
-          This option adds support for the raw1394 device file which enables
-          direct communication of user programs with IEEE 1394 devices
-          (isochronous and asynchronous).  Almost all application programs
-          which access FireWire require this option.
-          To compile this driver as a module, say M here: the module will be
-          called raw1394.
-          NOTE:
-          raw1394 is superseded by the newer firewire-core driver. See
-          http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for
-          further information on how to switch to the new FireWire drivers.
-config IEEE1394_VIDEO1394
-        tristate "video1394 userspace interface"
-        depends on IEEE1394 && IEEE1394_OHCI1394
-        help
-          This option adds support for the video1394 device files which enable
-          isochronous communication of user programs with IEEE 1394 devices,
-          especially video capture or export.  This interface is used by all
-          libdc1394 based programs and by several other programs, in addition to
-          the raw1394 interface.  It is generally not required for DV capture.
-          To compile this driver as a module, say M here: the module will be
-          called video1394.
-          NOTE:
-          video1394 is superseded by the newer firewire-core driver. See
-          http://ieee1394.wiki.kernel.org/index.php/Juju_Migration for
-          further information on how to switch to the new FireWire drivers.
-config IEEE1394_DV1394
-        tristate "dv1394 userspace interface (deprecated)"
-        depends on IEEE1394 && IEEE1394_OHCI1394
-        help
-          The dv1394 driver is unsupported and may be removed from Linux in a
-          future release.  Its functionality is now provided by either
-          raw1394 or firewire-core together with libraries such as libiec61883.
-config IEEE1394_VERBOSEDEBUG
-        bool "Excessive debugging output"
-        depends on IEEE1394
-        help
-          If you say Y here, you will get very verbose debugging logs from the
-          ieee1394 drivers, including sent and received packet headers.  This
-          will quickly result in large amounts of data sent to the system log.
-          Say Y if you really need the debugging output.  Everyone else says N.

diff --git a/drivers/ieee1394/Kconfig b/drivers/ieee1394/Kconfig deleted file mode 100644 index e02096cf7d95..000000000000 --- a/drivers/ieee1394/Kconfig +++ /dev/null
@@ -1,182 +0,0 @@
1	config IEEE1394
2	tristate "Legacy alternative FireWire driver stack"
3	depends on PCI \|\| BROKEN
4	help
5	IEEE 1394 describes a high performance serial bus, which is also
6	known as FireWire(tm) or i.Link(tm) and is used for connecting all
7	sorts of devices (most notably digital video cameras) to your
8	computer.
9
10	If you have FireWire hardware and want to use it, say Y here. This
11	is the core support only, you will also need to select a driver for
12	your IEEE 1394 adapter.
13
14	To compile this driver as a module, say M here: the module will be
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
22	config IEEE1394_OHCI1394
23	tristate "OHCI-1394 controllers"
24	depends on PCI && IEEE1394
25	help
26	Enable this driver if you have an IEEE 1394 controller based on the
27	OHCI-1394 specification. The current driver is only tested with OHCI
28	chipsets made by Texas Instruments and NEC. Most third-party vendors
29	use one of these chipsets. It should work with any OHCI-1394
30	compliant card, however.
31
32	To compile this driver as a module, say M here: the module will be
33	called ohci1394.
34
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
40	If you want to install firewire-ohci and ohci1394 together, you
41	should configure them only as modules and blacklist the driver(s)
42	which you don't want to have auto-loaded. Add either
43
44	blacklist ohci1394
45	blacklist video1394
46	blacklist dv1394
47	or
48	blacklist firewire-ohci
49
50	to /etc/modprobe.conf or /etc/modprobe.d/* and update modprobe.conf
51	depending on your distribution.
52
53	comment "PCILynx controller requires I2C"
54	depends on IEEE1394 && I2C=n
55
56	config IEEE1394_PCILYNX
57	tristate "PCILynx controller"
58	depends on PCI && IEEE1394 && I2C
59	select I2C_ALGOBIT
60	help
61	Say Y here if you have an IEEE-1394 controller with the Texas
62	Instruments PCILynx chip. Note: this driver is written for revision
63	2 of this chip and may not work with revision 0.
64
65	To compile this driver as a module, say M here: the module will be
66	called pcilynx.
67
68	Only some old and now very rare PCI and CardBus cards and
69	PowerMacs G3 B&W contain the PCILynx controller. Therefore
70	almost everybody can say N here.
71
72	comment "SBP-2 support (for storage devices) requires SCSI"
73	depends on IEEE1394 && SCSI=n
74
75	config IEEE1394_SBP2
76	tristate "Storage devices (SBP-2 protocol)"
77	depends on IEEE1394 && SCSI
78	help
79	This option enables you to use SBP-2 devices connected to an IEEE
80	1394 bus. SBP-2 devices include storage devices like harddisks and
81	DVD drives, also some other FireWire devices like scanners.
82
83	You should also enable support for disks, CD-ROMs, etc. in the SCSI
84	configuration section.
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
94	config IEEE1394_SBP2_PHYS_DMA
95	bool "Enable replacement for physical DMA in SBP2"
96	depends on IEEE1394_SBP2 && VIRT_TO_BUS && EXPERIMENTAL
97	help
98	This builds sbp2 for use with non-OHCI host adapters which do not
99	support physical DMA or for when ohci1394 is run with phys_dma=0.
100	Physical DMA is data movement without assistance of the drivers'
101	interrupt handlers. This option includes the interrupt handlers
102	that are required in absence of this hardware feature.
103
104	This option is buggy and currently broken on some architectures.
105	If unsure, say N.
106
107	config IEEE1394_ETH1394_ROM_ENTRY
108	depends on IEEE1394
109	bool
110	default n
111
112	config IEEE1394_ETH1394
113	tristate "IP networking over 1394 (experimental)"
114	depends on IEEE1394 && EXPERIMENTAL && INET
115	select IEEE1394_ETH1394_ROM_ENTRY
116	help
117	This driver implements a functional majority of RFC 2734: IPv4 over
118	1394. It will provide IP connectivity with implementations of RFC
119	2734 found on other operating systems. It will not communicate with
120	older versions of this driver found in stock kernels prior to 2.6.3.
121	This driver is still considered experimental. It does not yet support
122	MCAP, therefore multicast support is significantly limited.
123
124	The module is called eth1394 although it does not emulate Ethernet.
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
131	config IEEE1394_RAWIO
132	tristate "raw1394 userspace interface"
133	depends on IEEE1394
134	help
135	This option adds support for the raw1394 device file which enables
136	direct communication of user programs with IEEE 1394 devices
137	(isochronous and asynchronous). Almost all application programs
138	which access FireWire require this option.
139
140	To compile this driver as a module, say M here: the module will be
141	called raw1394.
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
148	config IEEE1394_VIDEO1394
149	tristate "video1394 userspace interface"
150	depends on IEEE1394 && IEEE1394_OHCI1394
151	help
152	This option adds support for the video1394 device files which enable
153	isochronous communication of user programs with IEEE 1394 devices,
154	especially video capture or export. This interface is used by all
155	libdc1394 based programs and by several other programs, in addition to
156	the raw1394 interface. It is generally not required for DV capture.
157
158	To compile this driver as a module, say M here: the module will be
159	called video1394.
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
166	config IEEE1394_DV1394
167	tristate "dv1394 userspace interface (deprecated)"
168	depends on IEEE1394 && IEEE1394_OHCI1394
169	help
170	The dv1394 driver is unsupported and may be removed from Linux in a
171	future release. Its functionality is now provided by either
172	raw1394 or firewire-core together with libraries such as libiec61883.
173
174	config IEEE1394_VERBOSEDEBUG
175	bool "Excessive debugging output"
176	depends on IEEE1394
177	help
178	If you say Y here, you will get very verbose debugging logs from the
179	ieee1394 drivers, including sent and received packet headers. This
180	will quickly result in large amounts of data sent to the system log.
181
182	Say Y if you really need the debugging output. Everyone else says N.