From: Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.19pre3
Date: Fri, 22 Dec 2000 21:33:58 +0200 [thread overview]
Message-ID: <20001222213358.A5829@elektroni.ee.tut.fi> (raw)
In-Reply-To: <E149GRm-0003sX-00@the-village.bc.nu>
In-Reply-To: <E149GRm-0003sX-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Dec 22, 2000 at 12:52:32AM +0000
On Fri, Dec 22, 2000 at 12:52:32AM +0000, Alan Cox wrote:
>
> 2.2.19pre3
> o Fix e820 handling (Andrea Arcangeli)
arch/i386/kernel/setup.c:
/* compare results from other methods and take the greater */
if (ALT_MEM_K < EXT_MEM_K) {
mem_size = EXT_MEM_K;
who = "BIOS-88";
} else {
mem_size = ALT_MEM_K;
who = "BIOS-e801";
}
e820.nr_map = 0;
- add_memory_region(0, LOWMEMSIZE(), E820_RAM);
- add_memory_region(HIGH_MEMORY, mem_size << 10, E820_RAM);
+ add_memory_region(0, i386_endbase, E820_RAM);
+ add_memory_region(HIGH_MEMORY, (mem_size << 10)-HIGH_MEMORY,
+ E820_RAM);
I think in case of BIOS-88 it now sees 1 Meg less than should. int 15, ah=88
gives the amount of extended memory above 1 Meg and it gets copied to
EXT_MEM_K. So HIGH_MEMORY should not be subtracted from it. (On the other
hand in case of BIOS-e801 ALT_MEM_K includes lower memory. I guess the
direct comparison of memory sizes ALT_MEM_K and EXT_MEM_K is not ok.)
linux-2.2.19pre3 on my 486 with 49152 k of RAM:
BIOS-provided physical RAM map:
BIOS-88: 000a0000 @ 00000000 (usable)
BIOS-88: 02e00000 @ 00100000 (usable)
Memory: 46128k/48128k available
linux-2.2.18 or linux-2.2.19pre2 :
Memory: 47144k/49152k available
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-22 20:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-22 0:52 Alan Cox
2000-12-22 3:40 ` Mitch Adair
2000-12-22 15:32 ` Petri Kaukasoina
2000-12-22 15:53 ` Richard B. Johnson
2000-12-22 16:02 ` Chad Schwartz
2000-12-22 16:23 ` Alan Cox
2000-12-22 16:25 ` Chad Schwartz
2000-12-22 16:43 ` Richard B. Johnson
2000-12-22 17:54 ` Miquel van Smoorenburg
2000-12-22 18:13 ` Richard B. Johnson
2000-12-22 16:21 ` Alan Cox
2000-12-22 19:33 ` Petri Kaukasoina [this message]
2000-12-22 19:56 ` Andrea Arcangeli
2000-12-23 12:05 ` Willy Tarreau
2000-12-28 1:18 ` Matthias Andree
2000-12-28 2:37 ` Alan Cox
2000-12-28 10:23 ` Matthias Andree
2000-12-28 12:20 ` Alan Cox
2000-12-28 13:53 ` Linux 2.2.18: /proc/apm slows system time (was: Linux 2.2.19pre3) Matthias Andree
2000-12-28 14:14 ` Matthias Andree
2000-12-29 12:42 ` Erik Mouw
2000-12-30 12:39 ` Matthias Andree
2000-12-30 17:01 ` Alan Cox
2000-12-30 17:38 ` Erik Mouw
2000-12-30 17:50 ` Alan Cox
2000-12-30 17:39 ` Matthias Andree
2000-12-31 10:34 ` Matthias Andree
2000-12-31 11:28 ` Chris Wedgwood
2000-12-31 13:32 ` Alan Cox
2001-01-02 13:52 ` [PATCH] CMOS locking for 2.4 (was: /proc/apm slows system time) Paul Gortmaker
2000-12-31 13:37 ` Linux 2.2.18: /proc/apm slows system time (was: Linux 2.2.19pre3) Alan Cox
2000-12-31 15:50 ` Erik Mouw
2000-12-31 16:13 ` Alan Cox
2001-01-02 16:32 ` Matthias Andree
2001-01-02 17:31 ` Alan Cox
2001-01-03 22:02 ` Matthias Andree
2000-12-28 11:14 ` Linux 2.2.19pre3 Guest section DW
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=20001222213358.A5829@elektroni.ee.tut.fi \
--to=kaukasoi@elektroni.ee.tut.fi \
--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®