[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 5/10]: Fix multiboot2 build on sparc
From: |
Robert Millan |
Subject: |
Re: [PATCH 5/10]: Fix multiboot2 build on sparc |
Date: |
Fri, 6 Mar 2009 19:58:31 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Wed, Mar 04, 2009 at 05:32:25PM -0800, David Miller wrote:
>
> 2009-03-03 David S. Miller <address@hidden>
>
> * loader/ieee1275/multiboot2.c (grub_mb2_arch_boot): Handle
> sparc like powerpc.
> ---
> loader/ieee1275/multiboot2.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/loader/ieee1275/multiboot2.c b/loader/ieee1275/multiboot2.c
> index c253fc9..6d0e781 100644
> --- a/loader/ieee1275/multiboot2.c
> +++ b/loader/ieee1275/multiboot2.c
> @@ -115,7 +115,7 @@ grub_mb2_arch_unload (struct multiboot_tag_header *tags)
> void
> grub_mb2_arch_boot (grub_addr_t entry_addr, void *tags)
> {
> -#if defined(__powerpc__)
> +#if defined(__powerpc__) || defined(__sparc__)
> kernel_entry_t entry = (kernel_entry_t) entry_addr;
> entry (MULTIBOOT2_BOOTLOADER_MAGIC, tags, grub_ieee1275_entry_fn, 0, 0);
> #elif defined(__i386__)
I'd rather refrain from enabling multiboot2 on sparc for now. The current
multiboot2 implementation needs a lot of work to be resynced/factorized with
the multiboot1 one. I'd expect it'd have to be almost replaced completely.
--
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."