mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Warren Togami <warren@togami.com>
To: linux-kernel@vger.kernel.org
Subject: 32bit agpgart + DRI on AMD64 K8 chipset
Date: Wed, 29 Oct 2003 23:58:16 -1000	[thread overview]
Message-ID: <1067507896.26667.22.camel@laptop> (raw)

Software:
Fedora Core 0.95 x86
Hardware:
MSI Neo Athlon64 3200+
VIA north and southbridge
Built by ATI Radeon 9200 128MB

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=107805
Please read this report for lspci, dmesg, XFree86.0.log and other
information relating to this problem.

I was having trouble getting my Radeon 9200 working properly with DRI 3D
acceleration.  DRI reports as "Yes" by glxinfo, but upon closer
inspection, the rawhide 2.4.22 based kernel was failing to load agpgart,
thus XFree86 was falling back successfully to pcigart.

(This problem is due to the existence of more than one "northbridge",
and the correct northbridge is actually onboard the AMD64 processor
itself.)

Dave Jones suggested that I try the agpgart improvements in Marcelo's
2.4.23-pre8.  I merged in everything from that patch that seemed
relevant (although I did not look at the drm improvements), and agpgart
now successfully loads.  Strangely though XFree86 still behaved with
equally slow behavior.  Inspection of XFree86.0.log revealed that it was
failing to use agpgart, and again falling back to pcigart.

Just to confirm that I didn't make any mistakes while merging, vanilla
2.4.23-pre8 exhibits the same behavior.

My unskilled cursory inspection of the drivers/char/agp/* code makes it
appear that the AMD_8151 stuff is intended to work only in x86_64 mode,
and it wasn't designed with 32bit in mind?  I guess not though...
because it compiles fine in 32bit.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=107805
Please read this report for more details about my testing.

Any ideas of other things to try?

Thanks,
Warren Togami
warren@togami.com



                 reply	other threads:[~2003-10-30  9:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1067507896.26667.22.camel@laptop \
    --to=warren@togami.com \
    --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®