From: Paul Nasrat <pauln@truemesh.com>
To: linux-8086@vger.kernel.org
Subject: History of the IBM PC and challenges for ELKS
Date: Wed, 11 Sep 2002 15:43:24 +0100 [thread overview]
Message-ID: <20020911144324.GF22803@raq465.uk2net.com> (raw)
As part of my talk to my LUG, I'd like to cover a brief history of the
IBM PC and the challenges of writing an OS for the architecture.
I know there was a thread on the list about the earlier models - haven't
found it in the archives yet. I've the stuff from the FAQ and various
resources on the IBM 5150, etc. I really need something quite quick and
snappy.
Can someone point me at some decent stuff or books on the hardware side:
CPU modes (real and protected)
Memory addressing (segments, flat)
Memory holes.
EMS, Extended, Expanded memory - are these relevant to elks
I don't want to talk at length on this stuff (but want to learn anyway),
but feel it'd be good to paint an overall picture.
Paul
next reply other threads:[~2002-09-11 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 14:43 Paul Nasrat [this message]
2002-09-11 16:46 ` History of the IBM PC and challenges for ELKS Feher Tamas
2002-09-11 21:55 ` Dan Olson
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=20020911144324.GF22803@raq465.uk2net.com \
--to=pauln@truemesh.com \
--cc=linux-8086@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