mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-kernel@vger.kernel.org
Cc: linux1394-devel@lists.sourceforge.net
Subject: [PATCH] ieee1394: schedule for removal
Date: Mon, 24 May 2010 21:31:23 +0200 (CEST)	[thread overview]
Message-ID: <tkrat.188ec405b9253375@s5r6.in-berlin.de> (raw)
In-Reply-To: <201005232348.o4NNm5kK024726@turbo.physics.adelaide.edu.au>

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.

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---

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(-)

Index: b/Documentation/feature-removal-schedule.txt
===================================================================
--- a/Documentation/feature-removal-schedule.txt
+++ 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 <hverkuil@xs4all.nl>
+
+----------------------------
+
+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 <stefanr@s5r6.in-berlin.de>
Index: b/drivers/ieee1394/Kconfig
===================================================================
--- a/drivers/ieee1394/Kconfig
+++ 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

-- 
Stefan Richter
-=====-==-=- -=-= ==---
http://arcgraph.de/sr/


       reply	other threads:[~2010-05-24 19:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4BF93F10.5070903@s5r6.in-berlin.de>
     [not found] ` <201005232348.o4NNm5kK024726@turbo.physics.adelaide.edu.au>
2010-05-24 19:31   ` Stefan Richter [this message]
2010-05-24 21:29     ` Jarod Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tkrat.188ec405b9253375@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®