All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Eric Lammerts <eric@lammerts.org>
Cc: video4linux-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix SAA7134 transport stream errors
Date: Thu, 3 Feb 2005 11:24:35 +0100	[thread overview]
Message-ID: <20050203102435.GC10602@bytesex> (raw)
In-Reply-To: <Pine.LNX.4.58.0502011901020.21364@vivaldi.madbase.net>

On Tue, Feb 01, 2005 at 08:19:17PM -0500, Eric Lammerts wrote:
> 
> Hi,
> I had a lot of problems with the transport stream input on the
> SAA7134. Even the slighest bit of other system activity caused data
> corruption. This patch corrects the switching of the two DMA
> buffers.

Thanks, merged (and fixed a simliar issue in saa7134-video.c along the
way ;).

> FYI, the problems only occur on Transmeta TM5800/TM5400 Crusoe boards
> (1GHz/533MHz). When I move the SAA7134 board to a 400MHz Celeron, no
> problems at all. I measured the interrupt latency of the SAA7134
> interrupt on the Crusoe, and that peaks to >1000us when power
> management is enabled and other activity (IDE DMA) is taking place!!
> That may explain why other people haven't seen this problem.

It has shown up before already (long ago), thats why the two-buffer
thingy exists in the first place.  Looks like 2.6 really makes a better
job on low-latency than 2.4 did, otherwise that would have been noticed
earlier...

  Gerd


      reply	other threads:[~2005-02-03 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02  1:19 [PATCH] Fix SAA7134 transport stream errors Eric Lammerts
2005-02-03 10:24 ` Gerd Knorr [this message]

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=20050203102435.GC10602@bytesex \
    --to=kraxel@bytesex.org \
    --cc=eric@lammerts.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=video4linux-list@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.