mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Jamie Lokier <jamie@shareable.org>
Cc: Paolo Ornati <javaman@katamail.com>, linux-kernel@vger.kernel.org
Subject: Re: [OT] Documentation for PC Architecture
Date: 19 Aug 2003 17:23:21 +0200	[thread overview]
Message-ID: <m34r0dbriu.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <20030819010205.GE11081@mail.jlokier.co.uk>

Jamie Lokier <jamie@shareable.org> writes:

> Paolo's question is, what happens to the 384k of _physical_ addresses
> starting at 0xa0000, which should correspond with 384k of actual
> physical RAM?

Part of it is used for BIOS (shadow of EPROM/flash EPROM - usually
written by BIOS executing from EPROM and then made read-only by
programming chipset registers). This involves main motherboard BIOS
(usually 64 KB at 0xF000-0xFFFF) and any extension BIOSes (VGA, LAN
etc) in 0xC000-0xEFFF (or 0xC000-0xDFFF) range.

The remaining RAM from 0xA000-0xFFFF is unusable. One could program
chipset registers to enable parts of this RAM. It would require
knowledge of particular chipset registers, and there might be only
one read-only/read-write bit for all shadows (so, unless you want the
shadow BIOS to be R/W, the additional RAM would have to be R/O).
RAM is quite cheap and these things are very non-standard so I think
nobody bothers.

And yes, older machines (older chipsets) used to remap fragments of
this memory to the top of RAM. It was common on 80286 machines and
I probably haven't seen a 386DX or faster board doing that.
-- 
Krzysztof Halasa
Network Administrator

  parent reply	other threads:[~2003-08-19 20:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-18  9:27 Paolo Ornati
2003-08-18 18:55 ` Herbert Pötzl
2003-08-18 21:11   ` Paolo Ornati
2003-08-18 22:54     ` Herbert Pötzl
2003-08-19  1:02       ` Jamie Lokier
2003-08-18 16:34         ` Nagendra Singh Tomar
2003-08-19 16:30           ` Jamie Lokier
2003-08-19  8:01         ` Paolo Ornati
2003-08-19 15:23         ` Krzysztof Halasa [this message]
2003-08-19  0:53     ` Jamie Lokier
2003-08-18 10:14 John Bradford
2003-08-18 11:24 ` Paolo Ornati
2003-08-19  7:37 John Bradford
2003-08-19 11:48 ` Maciej W. Rozycki

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=m34r0dbriu.fsf@defiant.pm.waw.pl \
    --to=khc@pm.waw.pl \
    --cc=jamie@shareable.org \
    --cc=javaman@katamail.com \
    --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

all inboxes | Powered by JetHome®