From: Thayne Harbaugh <tharbaugh@lnxi.com>
To: linux-kernel@vger.kernel.org
Cc: trivial@rustcorp.com.au, Eric Biederman <ebiederman@lnxi.com>
Subject: Re: [BUG][PATCH] BIOS reserved regions block iomem registration
Date: 22 Oct 2003 13:56:54 -0600 [thread overview]
Message-ID: <1066852614.6281.193.camel@tubarao> (raw)
In-Reply-To: <1066849062.6281.190.camel@tubarao>
[-- Attachment #1.1: Type: text/plain, Size: 354 bytes --]
> 1) Don't mark the BIOS reserved regions. Some BIOSes don't mark these
> and the kernel works fine. This is a trivial patch of removing the
> "reserved" line in setup.c:register_memory(). See
> remove_reserved.patch.
Er, the previous remove_reserved.patch wouldn't work. This should be
more correct.
--
Thayne Harbaugh
Linux Networx
[-- Attachment #1.2: remove_reserved-2.patch --]
[-- Type: text/plain, Size: 770 bytes --]
--- linux-2.4.20/arch/i386/kernel/setup.c 2002-11-28 16:53:09.000000000 -0700
+++ linux-2.4.20-bs/arch/i386/kernel/setup.c 2003-10-22 14:25:48.000000000 -0600
@@ -1042,12 +1042,14 @@
struct resource *res;
if (e820.map[i].addr + e820.map[i].size > 0x100000000ULL)
continue;
+ if (e820.map[i].type == E820_RESERVED)
+ continue;
res = alloc_bootmem_low(sizeof(struct resource));
switch (e820.map[i].type) {
case E820_RAM: res->name = "System RAM"; break;
case E820_ACPI: res->name = "ACPI Tables"; break;
case E820_NVS: res->name = "ACPI Non-volatile Storage"; break;
- default: res->name = "reserved";
+ default: res->name = "unknown";
}
res->start = e820.map[i].addr;
res->end = res->start + e820.map[i].size - 1;
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-22 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 18:57 Thayne Harbaugh
2003-10-22 19:56 ` Thayne Harbaugh [this message]
2003-10-24 4:21 ` Rusty Russell
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=1066852614.6281.193.camel@tubarao \
--to=tharbaugh@lnxi.com \
--cc=ebiederman@lnxi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/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®