From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: [PATCH] Add 2 more E820 to ACPI specification
Date: Fri, 15 Jan 2010 18:18:43 +0100 [thread overview]
Message-ID: <4B50A373.3060203@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 228 bytes --]
Hello. This defines 2 more types for mmap_type in a way to match E820
values. As grub legacy and grub2 both just pass E820 values through it
shouldn't be any problem.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: e820.diff --]
[-- Type: text/x-diff; name="e820.diff", Size: 778 bytes --]
=== modified file 'doc/multiboot.texi'
--- doc/multiboot.texi 2010-01-12 16:49:46 +0000
+++ doc/multiboot.texi 2010-01-15 16:52:03 +0000
@@ -817,7 +817,9 @@
can be greater than the minimum of 20 bytes. @samp{base_addr} is the
starting address. @samp{length} is the size of the memory region in bytes.
@samp{type} is the variety of address range represented, where a
-value of 1 indicates available @sc{ram}, and all other values currently
+value of 1 indicates available @sc{ram}, value of 3 indicates usable memory
+holding ACPI information, value of 4 indicates reserved memory which needs to
+be preserved on hibernation and all other values currently
indicated a reserved area.
The map provided is guaranteed to list all standard @sc{ram} that should
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next reply other threads:[~2010-01-15 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 17:18 Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-01-19 22:53 ` [PATCH] Add 2 more E820 to ACPI specification Robert Millan
2010-01-19 23:17 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-19 23:33 ` Robert Millan
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=4B50A373.3060203@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.