From: "David S. Miller" <davem@redhat.com>
To: rml@tech9.net
Cc: cyjamten@ihug.com.au, linux-kernel@vger.kernel.org
Subject: Re: AMD761Agpgart+Radeon64DDR+kernel+2.4.14...no go...
Date: Thu, 08 Nov 2001 16:45:39 -0800 (PST) [thread overview]
Message-ID: <20011108.164539.42460282.davem@redhat.com> (raw)
In-Reply-To: <1005239692.939.34.camel@phantasy>
In-Reply-To: <20011108123808.I27652@suse.de> <3BEA7525.7070807@ihug.com.au> <1005239692.939.34.camel@phantasy>
There are actually very huge issues with the AMD761 chipset and the
current AGPGART drivers. There are several hardware workarounds
necessary for that driver when using many AGP graphics cards, and I'm
trying to get info out of AMD to deal with this.
My radeon, which works perfectly fine with all current drivers on an
ALI based chipset, will lockup when running quake3 or even running one
of the xscreensaver OpenGL hacks.
I honestly got myself an ALI based board for my Athlon XP cpus when I
discovered these problems so that I can play quake3 while trying to
get the info out of AMD :-)
So that people don't think I'm talking out of my butt, have a look
at this:
http://www2.amd.com:80/us-en/assets/content_type/white_papers_and_tech_docs/24081.pdf
On page 210 there is a section titled "AGP Miniport Driver
Requirements", and to paraphrase this section basically tells
the reader "Yes, there are problems with some AGP cards and the
AMD761 chipset, to get that fixed just use our Windows drivers."
Anyone who reads the current agpgart amd761 support, can tell pretty
clearly that we don't have any of these mysterious workarounds
implemented.
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-11-09 0:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 4:11 disaster with 2.4.14+preempt J Sloan
2001-11-07 5:07 ` Robert Love
2001-11-07 6:52 ` J Sloan
2001-11-07 21:17 ` J Sloan
2001-11-08 3:48 ` preempt-patch cleared of blame J Sloan
2001-11-08 10:36 ` Jens Axboe
2001-11-08 12:23 ` Ingo Molnar
2001-11-08 11:38 ` Jens Axboe
2001-11-08 11:41 ` [patch] cciss dequeue race fix (was Re: preempt-patch cleared of blame) Jens Axboe
2001-11-08 12:05 ` AMD761Agpgart+Radeon64DDR+kernel+2.4.14...no go Cyrus
2001-11-08 22:04 ` Jussi Laako
2001-11-08 23:28 ` Alan Cox
2001-11-09 21:04 ` Jussi Laako
2001-11-15 23:25 ` Stephen C. Tweedie
2001-11-09 0:45 ` David S. Miller [this message]
2001-11-08 17:14 ` Robert Love
2001-11-11 7:59 ` AMD761Agpgart+Radeon64DDR+kernel+2.4.15-pre2...still testing Cyrus
2001-11-09 1:35 ` Success with 2.4.14 on Compaq 6500 J Sloan
2001-11-07 22:30 ` disaster with 2.4.14+preempt Robert Love
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=20011108.164539.42460282.davem@redhat.com \
--to=davem@redhat.com \
--cc=cyjamten@ihug.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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®