From: Mark Knecht <markknecht@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-rc1 - NForce4 PCI-E agpgart support?
Date: Wed, 16 Nov 2005 07:09:44 -0800 [thread overview]
Message-ID: <5bdc1c8b0511160709r47c1a9afk18e47a83ced2743d@mail.gmail.com> (raw)
In-Reply-To: <1132153102.2834.37.camel@laptopd505.fenrus.org>
On 11/16/05, Arjan van de Ven <arjan@infradead.org> wrote:
> On Wed, 2005-11-16 at 06:50 -0800, Mark Knecht wrote:
> > Hi,
> > I downloaded and built 2.6.15-rc1 as a test assuming Ingo will
> > release -rt support for this one of these days. (No rush Ingo!) It
> > booted on my AMD64 machine and is running fine AFAICT.
> >
> > One thing I was expecting to see was agpgart support for the
> > NForce4 chipset. Is this something that's coming or am I missing where
> > the configuration is done?
> >
> > I have a PCI-Express based Radeon and would like to get better
> > performance. I'm presuming that agpgart support is part of that
> > solution? (As it was on earlier architectures?)
>
> I'm pretty sure PCI-Express and AGP are mutually exclusive....
Ah, of course! My bad... They are different buses and connectors. I
was really thinking more of the 'gart' part of the agpgart.
Is there any requirement/need/value for something like a PCI-E-gart?
Or does this relocation requirement go out the window somehow when a
graphics device moves to PCI-Express?
Thanks,
Mark
next prev parent reply other threads:[~2005-11-16 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 14:50 Mark Knecht
2005-11-16 14:58 ` Arjan van de Ven
2005-11-16 15:09 ` Mark Knecht [this message]
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
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=5bdc1c8b0511160709r47c1a9afk18e47a83ced2743d@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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®