All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Nuno Silva <nuno.silva@vgertech.com>
Cc: Mark Knecht <markknecht@gmail.com>, "K.R. Foley" <kr@cybsft.com>,
	lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.14-rt1 - xruns in a certain circumstance
Date: Tue, 01 Nov 2005 02:37:57 -0500	[thread overview]
Message-ID: <1130830677.32101.101.camel@mindpipe> (raw)
In-Reply-To: <4366C95B.1040400@vgertech.com>

On Tue, 2005-11-01 at 01:48 +0000, Nuno Silva wrote:
> Mark Knecht wrote:
> 
> [..]
> 
> > I took a quick look. If you get a chance where does the NoAccel option
> > go? Inside of the section for the radeon driver? I'm sure I can find
> > this online but won't have much of an opportunity for the next few
> > hours.
> 
> IMHO this wont matter because, IIRC, the preview window in mythtv 
> doesn't even use xv... It's a straight x11 bitmap beeing drawn, after 
> scaling (so it's very CPU intensive... It's like having the HDD without 
> DMA enabled).

Does not matter, a buggy 2D XAA implementation can stall the PCI bus and
produce xruns.  I had an almost identical problem about a year ago with
the via driver and the gmplayer "splash screen" was the most reliable
way to trigger xruns.

Lee


  reply	other threads:[~2005-11-01  7:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31  2:28 2.6.14-rt1 - xruns in a certain circumstance Mark Knecht
2005-10-31  6:49 ` Lee Revell
2005-10-31 14:22 ` Ingo Molnar
2005-10-31 16:18   ` Lee Revell
2005-10-31 15:10 ` K.R. Foley
2005-10-31 15:26   ` Mark Knecht
2005-10-31 15:35     ` K.R. Foley
2005-10-31 16:39     ` Lee Revell
2005-10-31 17:38       ` Mark Knecht
2005-10-31 23:22       ` Mark Knecht
2005-11-01  1:48         ` Nuno Silva
2005-11-01  7:37           ` Lee Revell [this message]
2005-11-01  7:54           ` Lee Revell

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=1130830677.32101.101.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=kr@cybsft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markknecht@gmail.com \
    --cc=mingo@elte.hu \
    --cc=nuno.silva@vgertech.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.