linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: microcai <microcaicai@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [Question] Where is the missing 384k? Please, I've searching for it years!
Date: Mon, 09 May 2011 02:18:26 +0800	[thread overview]
Message-ID: <4DC6DE72.1000505@gmail.com> (raw)

It's being too long since I got this question.
I have to ask, even with a chance that I am considered as spam, and be
banned by kernel.org, I have to ask.
Please CC me if any one is going to answer my questions, I'll be
appreciate if you solve my haze.

So, my question is really simple, where is the missing 384k RAM?

When I read the books about PC, or see the output of dmesg, I've always
told that, 640k-1M is reserved for BIOS, and should not be used.

1)
384k RAM is reserved because BIOS is there. But I've heard that BIOS is
really in a ROM, not in RAM. So, where is the RAM when CPU is addressing
the ROM? Does the ROM just override the RAM and makes the RAM completely
un-addressable? What if people just got 2MB RAM? 384k of 2MB RAM is a
lot of wast!

2)
Is there a way to unmap the ROM and get back the RAM? or remap the 384k
RAM to upper address? If there is , why don't the kernel use this and
get my RAM(which is money) back?

3)
If there is not way to unmap the ROM or remap the RAM, why do they wast
384k RAM there! Even if 4G RAM is common now, 2M RAM is common in the
old days. Why did they do that!


Please help me to erase the big big question mark in my hart, Thanks!



             reply	other threads:[~2011-05-08 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-08 18:18 microcai [this message]
2011-05-09 13:40 ` [Question] Where is the missing 384k? Please, I've searching for it years! Phil Turmel
2011-05-09 18:20   ` microcai

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=4DC6DE72.1000505@gmail.com \
    --to=microcaicai@gmail.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;
as well as URLs for NNTP newsgroup(s).