From: "bibo,mao" <bibo.mao@intel.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: tgingold@free.fr
Subject: Re: Grub for ia64
Date: Thu, 28 Sep 2006 21:06:49 +0800 [thread overview]
Message-ID: <451BC8E9.7080905@intel.com> (raw)
In-Reply-To: <1159443706.451bb4fad4e1a@imp6-g19.free.fr>
It is great!!!, I will test on my IA64 box tommorrow. And I have few minor
comments like this.
whether kern/ia64/efi/init.c can be common for all architectures of efi
platform, only grub_arch_sync_caches is different, this function can be placed
on arch specific place. Function find_mmap_size can fit for all architectures.
why write different grub_efi_allocate_pages/grub_efi_free_boot_pages, we can
modify these two functions to fit for all architecture EFI platform.
thanks
bibo,mao
tgingold@free.fr wrote:
> Hi
>
> this is a port of grub2 to ia64. ia64 systems (itanium) are EFI based so this
> port reuse existing EFI infrastructure.
>
> I have made 4 patches:
>
> efi64.diffs: fix a 64 bits issue of efi/api.h
> fat.diffs: fix 64bits issues and make filename match case insensitive.
>
> [I think most 64 bits issues have already been reported recently and
> independently by the mail grub2 64bit system compatible]
>
> ia64.diffs: ia64 specific files
>
> modules.diffs:
> currently the ia64 port cannot load modules. This patch makes slight changes
> so that grub can be completly prelinked without removing the dynamic loading
> feature.
> I think it is worth for three reasons:
> * it makes initial port easier.
> * the current common code can't work on ia64 (on ia64 a function pointer is a
> descriptor and not the address of the first function instruction).
> * grub-emu doesn't have dynamic modules and could reuse this work to remove
> most of #ifdef/#endif GRUB_UTIL
>
> I have also written a few additionnal EFI specific commands I will post later.
>
> Tristan.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2006-09-28 13:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 11:41 Grub for ia64 tgingold
2006-09-28 13:06 ` bibo,mao [this message]
2006-09-28 13:12 ` tgingold
2006-09-28 13:33 ` Marco Gerards
2006-09-28 13:45 ` tgingold
2006-09-28 14:29 ` Marco Gerards
2006-09-28 14:49 ` tgingold
2006-09-29 5:10 ` Grub for ia64 - function descriptors Hollis Blanchard
2006-09-29 6:59 ` tgingold
2006-09-29 13:16 ` Hollis Blanchard
2006-10-02 6:31 ` tgingold
2006-10-03 2:17 ` Hollis Blanchard
2006-10-03 4:04 ` tgingold
2006-10-03 15:09 ` Hollis Blanchard
2006-09-28 13:47 ` Grub for ia64 Johan Rydberg
2006-09-28 13:35 ` tgingold
2006-09-28 14:15 ` Johan Rydberg
2006-09-28 13:38 ` Marco Gerards
2006-10-10 18:15 ` Johan Rydberg
2006-10-10 22:03 ` Jeff Bailey
2006-10-11 11:19 ` Johan Rydberg
2006-10-11 10:50 ` Tristan Gingold
-- strict thread matches above, loose matches on Subject: below --
2006-10-11 11:43 Mao, Bibo
2006-10-12 8:21 ` Tristan Gingold
2006-10-12 11:30 ` Johan Rydberg
2006-10-12 11:35 ` Tristan Gingold
2006-10-12 12:11 ` Johan Rydberg
2006-10-12 14:14 ` Tristan Gingold
2006-10-12 15:32 ` Johan Rydberg
2006-10-13 5:22 ` Tristan Gingold
2006-10-13 8:02 ` bibo,mao
2006-10-13 18:48 ` Yoshinori K. Okuji
2006-10-12 12:50 Mao, Bibo
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=451BC8E9.7080905@intel.com \
--to=bibo.mao@intel.com \
--cc=grub-devel@gnu.org \
--cc=tgingold@free.fr \
/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.