From: Otavio Salvador <otavio@debian.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] [PATCH] Add multiboot 2 capabilities
Date: Sat, 07 Jul 2007 15:12:07 -0300 [thread overview]
Message-ID: <87lkdsccco.fsf@lab.ossystems.com.br> (raw)
In-Reply-To: <9f50a7a00707070853i459cfe90h7f2c2c51d7123266@mail.gmail.com> (Jerone Young's message of "Sat, 7 Jul 2007 10:53:13 -0500")
"Jerone Young" <jerone@gmail.com> writes:
> diff -r b85dfdfcce16 conf/powerpc-ieee1275.rmk
> --- a/conf/powerpc-ieee1275.rmk Wed Jul 04 15:53:23 2007 -0500
> +++ b/conf/powerpc-ieee1275.rmk Thu Jul 05 08:04:34 2007 -0500
> @@ -102,7 +102,9 @@ pkgdata_MODULES = halt.mod \
> linux.mod \
> normal.mod \
> reboot.mod \
> - suspend.mod
> + suspend.mod \
> + _multiboot.mod \
> + multiboot.mod
Badly indented.
> # For _linux.mod.
> _linux_mod_SOURCES = loader/powerpc/ieee1275/linux.c
> @@ -140,5 +142,18 @@ halt_mod_CFLAGS = $(COMMON_CFLAGS)
> halt_mod_CFLAGS = $(COMMON_CFLAGS)
> halt_mod_LDFLAGS = $(COMMON_LDFLAGS)
>
> +# For _multiboot.mod
> +_multiboot_mod_SOURCES = loader/powerpc/ieee1275/multiboot2.c \
> + loader/multiboot2.c \
> + loader/multiboot_loader.c
> +_multiboot_mod_CFLAGS = $(COMMON_CFLAGS)
> +_multiboot_mod_LDFLAGS = $(COMMON_LDFLAGS)
> +
> +# For multiboot.mod
> +multiboot_mod_SOURCES = loader/multiboot_loader_normal.c
> +multiboot_mod_CFLAGS = $(COMMON_CFLAGS)
> +multiboot_mod_LDFLAGS = $(COMMON_LDFLAGS)
> +
> +
> include $(srcdir)/conf/common.mk
>
> diff -r b85dfdfcce16 include/grub/i386/pc/loader.h
> --- a/include/grub/i386/pc/loader.h Wed Jul 04 15:53:23 2007 -0500
> +++ b/include/grub/i386/pc/loader.h Thu Jul 05 01:17:47 2007 -0500
> @@ -22,11 +22,13 @@
<...>
> void EXPORT_FUNC(grub_linux_boot_zimage) (void) __attribute__ ((noreturn));
> void EXPORT_FUNC(grub_linux_boot_bzimage) (void) __attribute__ ((noreturn));
> @@ -34,16 +36,18 @@ void EXPORT_FUNC(grub_linux_boot_bzimage
> /* This is an asm part of the chainloader. */
> void EXPORT_FUNC(grub_chainloader_real_boot) (int drive, void *part_addr) __attribute__ ((noreturn));
>
> +
Useless change.
> /* The asm part of the multiboot loader. */
> void EXPORT_FUNC(grub_multiboot_real_boot) (grub_addr_t entry,
> struct grub_multiboot_info *mbi)
> + __attribute__ ((noreturn));
> +void EXPORT_FUNC(grub_multiboot2_real_boot) (grub_addr_t entry,
> + struct grub_multiboot_info *mbi)
> __attribute__ ((noreturn));
Use same codestyle, please.
There are some other places where it's not following same codestyle
and would be nice if it could be fixed, imho.
Kind regards,
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
next prev parent reply other threads:[~2007-07-07 18:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 15:53 [RFC] [PATCH] Add multiboot 2 capabilities Jerone Young
2007-07-07 18:12 ` Otavio Salvador [this message]
2007-07-08 8:25 ` Jerone Young
2007-07-22 13:22 ` Marco Gerards
2007-07-24 18:04 ` Jerone Young
2007-07-25 9:53 ` Marco Gerards
2007-07-25 10:03 ` Stefan Reinauer
2007-07-25 10:12 ` Marco Gerards
2007-07-25 12:54 ` Hollis Blanchard
2007-07-25 19:18 ` Jerone Young
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=87lkdsccco.fsf@lab.ossystems.com.br \
--to=otavio@debian.org \
--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.