From: Lee Revell <rlrevell@joe-job.com>
To: Mark Knecht <markknecht@gmail.com>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
Arjan van de Ven <arjan@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-rc1 - NForce4 PCI-E agpgart support?
Date: Wed, 16 Nov 2005 15:17:16 -0500 [thread overview]
Message-ID: <1132172237.3008.5.camel@mindpipe> (raw)
In-Reply-To: <5bdc1c8b0511161154y374b131jaa6c78badc221dd0@mail.gmail.com>
On Wed, 2005-11-16 at 11:54 -0800, Mark Knecht wrote:
> > The alternative is ATI's proprietary driver which probably already supports
> > your card.
>
> Thanks. I'll see if this old guitar player can get all of that done.
Mark,
You should really decide whether you're more interested in 100% xrun
free audio performance OR better video performance and pursue one or the
other - if you try to work on these in parallel you'll find it's one
step forward, two steps back. There have been many cases in the past
where video drivers ended up doing evil things that would ruin reliable
audio performance to get 0.1% better numbers on some Windows benchmark,
then the same bad behavior got ported over to Linux. I'd be especially
cautious with the Radeon driver as much of it seems to be reverse
engineered. And if you read the "X spinning in the kernel" thread you
see that apparently these GPUs can "crash" (!) in which case you seem to
be screwed.
Lee
next prev parent reply other threads:[~2005-11-16 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 14:50 2.6.15-rc1 - NForce4 PCI-E agpgart support? Mark Knecht
2005-11-16 14:58 ` Arjan van de Ven
2005-11-16 15:09 ` Mark Knecht
2005-11-16 18:02 ` Alistair John Strachan
2005-11-16 18:25 ` Mark Knecht
2005-11-16 18:49 ` Alistair John Strachan
2005-11-16 19:54 ` Mark Knecht
2005-11-16 20:17 ` Lee Revell [this message]
2005-11-16 21:26 ` Mark Knecht
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=1132172237.3008.5.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=s0348365@sms.ed.ac.uk \
/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