From: Dave Jones <davej@redhat.com>
To: Ryan Reich <ryanr@uchicago.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Overlapping MTRRs in 2.6.1
Date: Mon, 19 Jan 2004 14:59:55 +0000 [thread overview]
Message-ID: <20040119145955.GA22265@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401190818450.1003@ryanr.aptchi.homelinux.org>
On Mon, Jan 19, 2004 at 08:19:49AM -0600, Ryan Reich wrote:
> > Make sure you're loading both the agpgart module, *AND* the
> > relevant chipset driver for your board, ie via-agp, intel-agp or the like.
>
> Thanks, that's what I was doing. I didn't notice that the system had changed
> from 2.4.
It's mentioned in the http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt
document I wrote, which is 'must read' material if you're coming from 2.4 with
no idea of what changed from a user point of view.
Dave
next prev parent reply other threads:[~2004-01-19 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 21:11 Overlapping MTRRs in 2.6.1 Ryan Reich
2004-01-18 21:57 ` Mike Fedyk
2004-01-19 1:21 ` Ryan Reich
2004-01-19 9:50 ` Dave Jones
2004-01-19 14:19 ` Ryan Reich
2004-01-19 14:59 ` Dave Jones [this message]
2004-01-19 15:16 ` Ryan Reich
[not found] <1fsuY-4YG-9@gated-at.bofh.it>
2004-01-18 23:25 ` Lenar Lõhmus
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=20040119145955.GA22265@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ryanr@uchicago.edu \
/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