From: Paolo Ornati <javaman@katamail.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Documentation for PC Architecture
Date: Tue, 19 Aug 2003 10:01:42 +0200 [thread overview]
Message-ID: <200308191001.42094.javaman@katamail.com> (raw)
In-Reply-To: <20030819010205.GE11081@mail.jlokier.co.uk>
On Tuesday 19 August 2003 03:02, Jamie Lokier wrote:
>
> The MMU _is_ used to remap memory addresses. It is part of the CPU itself.
> But it translates what's called "virtual address" space to "physical
> address space". Physical addresses seemingly map directly to RAM and
> memory-mapped I/O.
I know...
>
> Paolo's question is, what happens to the 384k of _physical_ addresses
> starting at 0xa0000, which should correspond with 384k of actual
> physical RAM?
It seems that only you have understand my question! :-)
>
> If you use the MMU to map a virtual address to the physical addresses from
> 0xa0000..0xfffff, then whichever virtual addresses you chose will map to
> video memory, ROM, BIOS etc.
>
> The answer is that after the MMU has translated, a _second_ address
> translation takes place, outside the CPU, which maps the physical addresses
> so that a hole is created in the RAM without any RAM going missing. This
> second translation is done by the motherboard chipset.
OK.
>
> Enjyo,
> -- Jamie
VERY [OT]:
Why do I do all these questions?
At present I'm working on a very small kernel (PabloX :):
- it's very simple: it only uses segmentation and has drivers only for stupid
things like AT-PS/2 keyboard (do you have USB keyboard? I'm sorry!)
- some (a lot of) code is taken from linux 0.01 / 1.0 / ...
If anyone want to see this stupid thing:
http://members.xoom.virgilio.it/javaman/
NOTE: don't read the comments in source code! They are a mix of pseudo-English
and Italian!
To try it:
tar xzf pablox.tar.gx
cd pablox/
make
now you should have a floppy image in ./IMAGE, I suggest insert a floppy and
do "make disk", than reboot and see keyboard leds! (if you have an AT or PS/2
keyboard)
press (1,2,3,4) to switch to console (1,2,3,4): the consoles are stupid! All
the programs write to the current console...
press "ESC" to reboot!
Bye,
Paolo
next prev parent reply other threads:[~2003-08-19 8:01 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 [this message]
2003-08-19 15:23 ` Krzysztof Halasa
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=200308191001.42094.javaman@katamail.com \
--to=javaman@katamail.com \
--cc=jamie@shareable.org \
--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®