From: William Lee Irwin III <wli@holomorphy.com>
To: Timothy Miller <miller@techsource.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PCI mapping on large memory 32-bit machines
Date: Mon, 19 May 2003 15:59:04 -0700 [thread overview]
Message-ID: <20030519225904.GI8978@holomorphy.com> (raw)
In-Reply-To: <3EC91F3B.8010005@techsource.com>
On Mon, May 19, 2003 at 02:15:23PM -0400, Timothy Miller wrote:
> On x86 with PAE and 4 gigs of RAM or more, where do memory-mapped I/O
> devices get mapped (in the physical address space)? Most PCI devices
> can't handle 64-bit addresses. Can PC chipsets physically remap some of
> the RAM to above 4 gig? Or do you just lose that much RAM? If both RAM
> and some I/O device are mapped to the same location, isn't there a conflict?
AFAIK most (if not all) of that lands below 4GB in extant chipsets/BIOS's.
Remapping above 4GB is possible but various things would probably barf.
-- wli
prev parent reply other threads:[~2003-05-19 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 18:15 PCI mapping on large memory 32-bit machines Timothy Miller
2003-05-19 18:25 ` Richard B. Johnson
2003-05-19 22:59 ` William Lee Irwin III [this message]
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=20030519225904.GI8978@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
/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.