All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Add 2 more E820 to ACPI specification
Date: Wed, 20 Jan 2010 00:33:33 +0100	[thread overview]
Message-ID: <20100119233333.GO8599@thorin> (raw)
In-Reply-To: <4B563D86.1000103@gmail.com>

On Wed, Jan 20, 2010 at 12:17:26AM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Robert Millan wrote:
> > On Fri, Jan 15, 2010 at 06:18:43PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> >   
> >> 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.
> >>     
> >
> > Note that although Multiboot's memory map format is modelled after e820,
> > it is defined by us, not by BIOS vendors.
> >
> >   
> Yes, but this information is needed and I prefer to provide it in
> grub-legacy-compatible way.
> >> -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,
> >>     
> >
> > I'm concerned about increasing the amount of arch-specific references; what do
> > Multiboot kernels that use ACPI currently do?
> >
> >   
> According to a post by Bernard Trotter many of them rely on multiboot
> loader passing e820 through

I just checked GRUB Legacy;  it seems that it is passing through the whole
thing.  I think this was a mistake, but it's too late to fix it now.

Feel free to commit this.

-- 
Robert Millan

  "Be the change you want to see in the world" -- Gandhi



      reply	other threads:[~2010-01-19 23:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-15 17:18 [PATCH] Add 2 more E820 to ACPI specification Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-19 22:53 ` Robert Millan
2010-01-19 23:17   ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-19 23:33     ` Robert Millan [this message]

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=20100119233333.GO8599@thorin \
    --to=rmh@aybabtu.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.