From: Daniel Drake <dsd@gentoo.org>
To: davej@codemonkey.org.uk
Cc: linux list <linux-kernel@vger.kernel.org>
Subject: amd64 agpgart aperture base value
Date: Wed, 13 Dec 2006 22:47:32 -0500 [thread overview]
Message-ID: <4580C954.103@gentoo.org> (raw)
Hi Dave,
I'm working on a solution for
http://bugzilla.kernel.org/show_bug.cgi?id=6350
Certain BIOSes are screwing with the K8 aperture base value. However,
these systems work after booting into windows and then rebooting into Linux.
It originally appeared to be a bug specific to asrock motherboard based
on nforce3, but further reports have shown that this bug also manifests
on ASUS+nforce3 and ASUS+via.
The BIOS sets some high bits at address 0x94 of the PCI config space of
the northbridge, which falls under AMD64_GARTAPERTUREBASE
My current approach at a solution involves identifying the buggy systems
by southbridge, and then fixing the northbridge in a PCI quirk. However
as more systems are being uncovered I don't feel so good about this
approach.
In amd64-agp.c, would it be dangerous to remove the "aperture base > 4G"
thing and instead simply only read the rightmost 7 bits to ensure the
aperture base is always in range? (This is coming from someone with
little AGPGART understanding...)
Alternatively do you have other suggestions for how the problem might be
solved better?
Thanks!
Daniel
next reply other threads:[~2006-12-14 4:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 3:47 Daniel Drake [this message]
2006-12-14 13:22 ` amd64 agpgart aperture base value Dave Jones
2006-12-14 23:35 ` Daniel Drake
2006-12-15 0:02 ` Dave Jones
2006-12-18 11:38 ` Eric W. Biederman
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=4580C954.103@gentoo.org \
--to=dsd@gentoo.org \
--cc=davej@codemonkey.org.uk \
--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 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.