From: Dan Dennedy <dan@dennedy.org>
To: linux1394-devel@lists.sourceforge.net
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
Adrian Bunk <bunk@stusta.de>,
scjody@modernduck.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] the overdue removal of RAW1394_REQ_ISO_{LISTEN,SEND}
Date: Sat, 8 Apr 2006 12:18:24 -0700 [thread overview]
Message-ID: <200604081218.24544.dan@dennedy.org> (raw)
In-Reply-To: <44374FC0.3070507@s5r6.in-berlin.de>
On Friday 07 April 2006 22:53, Stefan Richter wrote:
> Adrian Bunk wrote:
> > This patch contains the overdue removal of the RAW1394_REQ_ISO_SEND and
> > RAW1394_REQ_ISO_LISTEN request types plus all support code for them.
>
> [...]
>
> I am not familiar with the isochronous part of Linux' 1394 software
> stack, so I can't comment whether there are high-profile applications
> which still did not migrate away from this interface, or did so only
> recently.
Kino still uses the legacy raw1394 iso interface for capture by default;
however, it can also still use dv1394. I will accellerate the adoption of the
new raw1394 interface since I have already done this for dvgrab 2.0.
Cinelerra supports libiec61883 now.
Unfortunately, gstreamer still uses legacy raw1394 iso interface, but I can
nag someone at Fluendo. I think another high profile app that might be
affected is GnomeMeeting/Ekiga, but I have not kept close track of it.
Also, I have not released a version of libraw1394 that contains the
deprecation warnings, but I can do so this weekend. And then another release
when the removed kernel interfaces are released that removes the functions.
next prev parent reply other threads:[~2006-04-08 19:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 22:47 [RFC: 2.6 patch] the overdue removal of RAW1394_REQ_ISO_{LISTEN,SEND} Adrian Bunk
2006-04-07 0:35 ` Gene Heskett
2006-04-07 0:40 ` Lee Revell
2006-04-07 1:13 ` Gene Heskett
2006-04-07 2:09 ` Gene Heskett
2006-04-07 5:52 ` Denis Vlasenko
2006-04-07 6:15 ` Gene Heskett
2006-04-08 5:53 ` Stefan Richter
2006-04-08 19:18 ` Dan Dennedy [this message]
2006-04-08 19:49 ` Stefan Richter
2006-04-08 19:53 ` Stefan Richter
2006-04-18 9:45 ` Jody McIntyre
2006-04-18 23:59 ` Dan Dennedy
2006-04-09 1:25 ` Dan Dennedy
2006-04-18 9:48 ` Jody McIntyre
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=200604081218.24544.dan@dennedy.org \
--to=dan@dennedy.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=scjody@modernduck.com \
--cc=stefanr@s5r6.in-berlin.de \
/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