From: Andi Kleen <andi@firstfloor.org>
To: Chris Adams <cmadams@hiwaay.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AGP aperture beyond 4GB not valid?
Date: Wed, 13 Aug 2008 04:38:04 +0200 [thread overview]
Message-ID: <87k5el1vxv.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080813013255.GD633804@hiwaay.net> (Chris Adams's message of "Tue, 12 Aug 2008 20:32:55 -0500")
Chris Adams <cmadams@hiwaay.net> writes:
>
> My BIOS doesn't have an IOMMU option (latest BIOS available for the
> mboard). However, it appears that an aperture is allocated but the
> kernel then ignores it due to where it is placed. Why?
32MB is normally not a useful aperture. Likely it's some garbage
value the BIOS is leaving in the registers.
> Is there anything I can or should do about this (what impact does this
> really have)?
It will eat your babies. No really except for some lost RAM nothing.
-Andi
next prev parent reply other threads:[~2008-08-13 2:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 1:32 AGP aperture beyond 4GB not valid? Chris Adams
2008-08-13 2:38 ` Andi Kleen [this message]
2008-08-13 6:01 ` H. Peter Anvin
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=87k5el1vxv.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=cmadams@hiwaay.net \
--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