Skip to contentSkip to conversation

ieee1394: schedule for removal

PATCH In review Stefan Richter 2 participants 2 messages May 24, 2010 2 messages not in the archive Documentation

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

PATCH 1/1 ieee1394: schedule for removal

All application domains that are supported by the old ieee1394 driver stack are supported by the newer firewire driver stack too. (FireWire audio came last, in 2.6.32.) There is now good and extensive experience with the newer stack from deployment in Fedora since F7 as well as by enthusiast users of other distributions. The new drivers have consequently been recommended as the default ones since 2.6.33, in order to fix some severe usability problems of FireWire on Linux due to limitations of the old stack. It is now high time to announce when the obsolete drivers will be removed.

---

Removal in 2.6.36 should be OK too, but one of the Linux FireWire audio driver (ffado) developers recommended 2.6.37 since the current generation of pro-audio oriented distributions still ships the old drivers as default.

 Documentation/feature-removal-schedule.txt |   10 ++++++++++
 drivers/ieee1394/Kconfig                   |    4 ++--
 2 files changed, 12 insertions(+), 2 deletions(-)
Documentation/feature-removal-schedule.txt +10 -0
Index: b/Documentation/feature-removal-schedule.txt
===================================================================
@@ -612,3 +612,13 @@ Why:	The vtx device nodes have been supe
 	provided by the vtx API, then that functionality should be build
 	around the sliced VBI API instead.
 Who:	Hans Verkuil <[email protected]>
+
+----------------------------
+
+What:	old ieee1394 subsystem (CONFIG_IEEE1394)
+When:	2.6.37
+Files:	drivers/ieee1394/ except init_ohci1394_dma.c
+Why:	superseded by drivers/firewire/ (CONFIG_FIREWIRE) which offers more
+	features, better performance, and better security, all with smaller
+	and more modern code base
+Who:	Stefan Richter <[email protected]>
drivers/ieee1394/Kconfig +2 -2
Index: b/drivers/ieee1394/Kconfig
===================================================================
@@ -1,5 +1,5 @@
 config IEEE1394
-	tristate "Legacy alternative FireWire driver stack"
+	tristate "Legacy alternative FireWire drivers (Obsolete, deprecated)"
 	depends on PCI || BROKEN
 	help
 	  IEEE 1394 describes a high performance serial bus, which is also
@@ -164,7 +164,7 @@ config IEEE1394_VIDEO1394
 	  further information on how to switch to the new FireWire drivers.
 
 config IEEE1394_DV1394
-	tristate "dv1394 userspace interface (deprecated)"
+	tristate "dv1394 userspace interface"
 	depends on IEEE1394 && IEEE1394_OHCI1394
 	help
 	  The dv1394 driver is unsupported and may be removed from Linux in a
Signature · 3 lines
Stefan Richter
-=====-==-=- -=-= ==---
http://arcgraph.de/sr/
Acked-by on v1 1/1
#3 lore raw
Quoted 11 lines · Stefan Richter

All application domains that are supported by the old ieee1394 driver stack are supported by the newer firewire driver stack too.  (FireWire audio came last, in 2.6.32.)  There is now good and extensive experience with the newer stack from deployment in Fedora since F7 as well as by enthusiast users of other distributions.  The new drivers have consequently been recommended as the default ones since 2.6.33, in order to fix some severe usability problems of FireWire on Linux due to limitations of the old stack.  It is now high time to announce when the obsolete drivers will be removed.

Good riddance.

Signature · 2 lines
Jarod Wilson
[email protected]