public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: hahn@physics.mcmaster.ca, linux-kernel@vger.kernel.org
Subject: Re: no more MTRRs available ?
Date: Wed, 29 Jan 2003 18:15:17 +0100	[thread overview]
Message-ID: <20030129181517.32f0ea49.skraw@ithnet.com> (raw)
In-Reply-To: <20030129162013.GA1856@codemonkey.org.uk>

On Wed, 29 Jan 2003 16:20:13 +0000
Dave Jones <davej@codemonkey.org.uk> wrote:

> On Wed, Jan 29, 2003 at 05:05:54PM +0100, Stephan von Krawczynski wrote:
> 
>  > Mark Hahn <hahn@physics.mcmaster.ca> wrote:
> 
> (odd, I'm not getting Mark's mails to l-k).

He does not send them there. I know it is a no-no to forward his writings to
the list, but I thought it may be of use to others, too (and he did not shoot
me for it so far ;-)

>  > > that your bios is stupid, I think.  mtrr's handle areas that are 
>  > > powers of two in size (and >= 1M, I think).  the problem here is that
>  > > the bios is trying to represent 4G of write-back ram and a 16M of 
>  > > uncachable IO area (AGP aperture, I'm guessing).  the correct way
>  > > to do this is a single 4G mtrr with an overlapping 16M one.
> 
> That does seem to make more sense. Perhaps too much sense.
> ISTR there were ordering rules in how you layer MTRRs on top of each
> other.

Ok, after reading your thoughts and re-reading the bios stuff I found and "DRAM
alignment" option, and voila:

reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
reg01: base=0x100000000 (4096MB), size=4096MB: write-back, count=1
reg02: base=0x200000000 (8192MB), size=8192MB: write-back, count=1
reg03: base=0x400000000 (16384MB), size=16384MB: write-back, count=1
reg04: base=0x800000000 (32768MB), size=32768MB: write-back, count=1
reg05: base=0xfb000000 (4016MB), size=   8MB: write-combining, count=1

The table got obviously shorter and significantly "better". It seems the
onboard VGA stuff is now mapped out of the normal DRAM range. 

I must admit though that some of this bios looks fishy, because now I cannot
find the original DRAM caching entries any longer, no matter what I switch on
or off (you know those "write-back, write-through" stuff).

Now I think one can really be content with this setup. Thanks a lot to Mark and
Dave.
In case anyone is interested, this is an Asus TRL-DLS mb.

-- 
Regards,
Stephan

  reply	other threads:[~2003-01-29 17:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 15:23 no more MTRRs available ? Stephan von Krawczynski
     [not found] ` <Pine.LNX.4.44.0301291025240.18828-100000@coffee.psychology.mcmaster.ca>
2003-01-29 15:45   ` Stephan von Krawczynski
     [not found]     ` <Pine.LNX.4.44.0301291046490.18828-100000@coffee.psychology.mcmaster.ca>
2003-01-29 16:05       ` Stephan von Krawczynski
2003-01-29 16:20         ` Dave Jones
2003-01-29 17:15           ` Stephan von Krawczynski [this message]
2003-01-29 16:14     ` Dave Jones
2003-01-29 16:52       ` Dave Jones
2003-01-29 17:20     ` William Lee Irwin III
2003-01-29 17:48       ` Dave Jones
2003-01-29 18:00         ` William Lee Irwin III
2003-01-29 18:12           ` 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=20030129181517.32f0ea49.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=davej@codemonkey.org.uk \
    --cc=hahn@physics.mcmaster.ca \
    --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