mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Bill Fink <billfink@mindspring.com>
Cc: linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	Harvey Harrison <harvey.harrison@gmail.com>
Subject: Re: [PATCH 2/2] ieee1934: dv1394 interrupt enabling/disabling broken on big-endian
Date: Sun, 14 Dec 2008 03:02:11 +0100	[thread overview]
Message-ID: <49446923.5040606@s5r6.in-berlin.de> (raw)
In-Reply-To: <20081213204137.d150645c.billfink@mindspring.com>

Bill Fink wrote:
> On Sun, 14 Dec 2008, Stefan Richter wrote:
>> Looks like a bug + correct fix indeed.  Apparently dv1394 was never used on big
>> endian PCs.
...
> I use dv1394 on a big-endian PPC system (2.6.15 kernel) to watch DV video
> via xine, and this has always worked fine for me.

Could you try to apply the patch to your kernel to test it?  You can get
it in plaintext e.g. from
http://user.in-berlin.de/~s5r6/linux1394/submitted/843-ieee1934-dv1394-interrupt-enabling_disabling-broken-on-big-endian.patch

> And this shouldn't be phased out until the equivalent functionality is
> added to ffmpeg via the new APIs.

Or perhaps by a dv1394 replacement module which plugs to the V4L2 API.
-- 
Stefan Richter
-=====-==--- ==-- -===-
http://arcgraph.de/sr/

  reply	other threads:[~2008-12-14  2:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13 23:21 Harvey Harrison
2008-12-14  0:41 ` Stefan Richter
2008-12-14  1:41   ` Bill Fink
2008-12-14  2:02     ` Stefan Richter [this message]
2008-12-23 22:23       ` Bill Fink
2008-12-26  3:02         ` Bill Fink
2009-01-03 16:50           ` Stefan Richter
2009-01-04  2:18             ` Bill Fink
2009-01-04 21:03               ` Stefan Richter

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=49446923.5040606@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=billfink@mindspring.com \
    --cc=harvey.harrison@gmail.com \
    --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®