All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Mark Watts <m.watts@eris.qinetiq.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Via KT400 agpgart issues
Date: Fri, 15 Aug 2003 12:07:00 +0100	[thread overview]
Message-ID: <20030815110700.GE22433@redhat.com> (raw)
In-Reply-To: <200308150859.03617.m.watts@eris.qinetiq.com>

On Fri, Aug 15, 2003 at 08:59:03AM +0100, Mark Watts wrote:

 > I thought the KT400 chipset (at least) had been backported to 2.4.21 ?

Only for AGP2.x mode.

 > I'm not experiancing any technical problems. The nvidia /proc interfaces are 
 > reporting that I'm running at agp 8x

if its using its own agpgart routines, maybe. If it isn't, it's broken,
or lying.

 > , and I have full hardware acceleration 
 > enough to play games like Unreal Tournament 2003 quite fast (~50fps), its 
 > just that agpgart cant find my aperature size...

which happens when agpgart tries to read the AGP2.x size, when the
chipset is in 3.x mode.

 > I just tried my vendors (mandrake) 2.4.22 kernel and I get exactly the same 
 > output.

No vendor that I know of has backported the AGP3 support it its
entirity. The closest to a backport so far is the trainwreck that
is the ATI FireGL drivers.

		Dave

-- 
 Dave Jones     http://www.codemonkey.org.uk

  reply	other threads:[~2003-08-15 11:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-14  9:25 Via KT400 agpgart issues Mark Watts
2003-08-14 10:50 ` Rahul Karnik
2003-08-14 18:48 ` Dave Jones
2003-08-15  7:59   ` Mark Watts
2003-08-15 11:07     ` Dave Jones [this message]
2003-08-14 18:53 ` dleonard
2003-08-14 18:50   ` Dave Jones

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=20030815110700.GE22433@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.watts@eris.qinetiq.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.