From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] decouple mmap parsing and implement Multiboot mmap in the loader
Date: Wed, 13 Aug 2008 21:51:09 +0200 [thread overview]
Message-ID: <20080813195109.GA22009@thorin> (raw)
In-Reply-To: <87skt8245g.fsf@xs4all.nl>
On Wed, Aug 13, 2008 at 07:52:59PM +0200, Marco Gerards wrote:
> > #include <grub/types.h>
> > #include <grub/symbol.h>
> > +#include <grub/multiboot.h> /* For struct grub_mmap_entry, which is also
> > + needed by Multiboot. */
>
> Isn't it better to split the header file? This seems like a hack.
The definition is part of the Multiboot spec, so it really needs to be present
in multiboot.h.
We could also define it separately as grub_mmap_entry in multiboot.h and keep
the grub_machine_mmap_entry definition in pc/init.h. Then other arches could
have their own grub_machine_mmap_entry variant which _does_ differ from
grub_mmap_entry (like coreboot).
What do you think?
> > Index: loader/i386/pc/multiboot.c
> > ===================================================================
> > --- loader/i386/pc/multiboot.c (revision 1802)
> > +++ loader/i386/pc/multiboot.c (working copy)
> > @@ -78,14 +78,60 @@
> > grub_free ((void *) mbi->cmdline);
> > grub_free (mbi);
> > }
> > -
> > -
> > +
>
> Hm? :-)
Some minor janitor work ;-)
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2008-08-13 19:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 15:22 [PATCH] decouple mmap parsing by using grub_available_iterate() Robert Millan
2008-08-11 15:39 ` Vesa Jääskeläinen
2008-08-11 21:24 ` Robert Millan
2008-08-11 22:07 ` Robert Millan
2008-08-12 13:25 ` [PATCH] decouple mmap parsing and implement Multiboot mmap in the loader Robert Millan
2008-08-12 16:29 ` Robert Millan
2008-08-12 22:38 ` Robert Millan
2008-08-12 23:44 ` Robert Millan
2008-08-13 17:52 ` Marco Gerards
2008-08-13 19:51 ` Robert Millan [this message]
2008-08-16 14:50 ` Marco Gerards
2008-08-17 16:31 ` 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=20080813195109.GA22009@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.