All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: IA64 port
Date: Tue, 29 Jan 2008 10:17:36 +0100	[thread overview]
Message-ID: <20080129091736.GG30048@thorin> (raw)
In-Reply-To: <20080129051252.GA2504@saphi>

On Tue, Jan 29, 2008 at 06:12:52AM +0100, Tristan Gingold wrote:
> > Have you checked if this trick works on other ports?  Maybe it'd be a good idea
> > to merge this first.
> 
> I don't really understand what do you mean by 'works on other ports'.  It is
> designed to be an optionnal feature used only by ia64.  Nothing IA64 specific
> and other ports may use it.  If we go this way, it would be good to slightly
> improve it.

I suggest you just make sure it'll be usable on other ports in case a need
arises, without going out of your way to support it.

> > > +GRUB_MOD_INIT(linux_normal)
> > > +{
> > > +  (void) mod; /* To stop warning.  */
> > > +  grub_register_command
> > > +    ("linux", grub_normal_linux_command,
> > > +     GRUB_COMMAND_FLAG_BOTH | GRUB_COMMAND_FLAG_NO_ARG_PARSE,
> > > +     "linux FILE [ARGS...]",
> > > +     "Load a linux kernel.", 0);
> > > +  
> > > +  grub_register_command
> > > +    ("initrd", grub_normal_initrd_command,
> > > +     GRUB_COMMAND_FLAG_BOTH | GRUB_COMMAND_FLAG_NO_ARG_PARSE,
> > > +     "initrd FILE",
> > > +     "Load an initrd.", 0);
> > > +
> > > +  grub_register_command
> > > +    ("module", grub_normal_cmd_module,
> > > +     GRUB_COMMAND_FLAG_BOTH | GRUB_COMMAND_FLAG_NO_ARG_PARSE,
> > > +     "module FILE [ARGS...]",
> > > +     "Load a Multiboot module.", 0);
> > 
> > Multiboot module loader in linux_normal.mod ?
> 
> Well, well well.  Long question :-)
> 
> Ia64 doesn't really fit in multiboot: it's a full 64 bits processor,

But there's multiboot2.

> there
> may be no room for an header in the 8KB (or you have to waste a lot of memory
> to keep alignment), no room for EFI pointers in the header and no Ia64 OS
> uses it.  Well this were my conclusion when I read MB specs.

Does this affect only EFI, or ia64 in general (e.g. ia64-coreboot, when that
exists) ?

Also note the string "Load a Multiboot module." is present.

If this is not multiboot, I'd suggest renaming the command to avoid name
collisions (not only if multiboot is added later, but also user confusion).

> > > diff -ruNp -x '*~' -x CVS grub2.orig/util/ia64/efi/elf2pe.c grub2/util/ia64/efi/elf2pe.c
> > > --- grub2.orig/util/ia64/efi/elf2pe.c	1970-01-01 01:00:00.000000000 +0100
> > > +++ grub2/util/ia64/efi/elf2pe.c	2008-01-28 16:29:58.000000000 +0100
> [...]
> > 
> > This utility seems to be usable on i386 too?  In that case, better to put it
> > outside ia64/ dir?
> 
> It should work on i386 too, but not tested.
> I have written this utility for my port of EFI and adapted the style for
> grub.  It may be nice to share this code with i386 but not really required
> now IMHO.

util/i386/efi/grub-mkimage.c already generates PE, right?  Why a different
way to handle this?  Sound like it'd be more consistent to either use elf2pe
on both or share the same grub-mkimage.  What do you think?
 
-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)



  reply	other threads:[~2008-01-29  9:19 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 16:09 IA64 port Tristan Gingold
2008-01-28 16:55 ` Robert Millan
2008-01-29  5:12   ` Tristan Gingold
2008-01-29  9:17     ` Robert Millan [this message]
2008-01-29 10:31       ` tgingold
2008-01-29 11:08         ` Robert Millan
2008-01-29  9:59     ` Robert Millan
2008-01-29 10:35       ` tgingold
2008-01-29 11:32         ` Robert Millan
2008-01-29 12:56           ` tgingold
2008-01-29 13:19             ` Robert Millan
2008-01-29 14:46               ` Marco Gerards
2008-01-29 15:30                 ` Robert Millan
2008-01-29 16:38                   ` tgingold
2008-01-29 18:48                     ` Robert Millan
2008-01-30  5:23                       ` Tristan Gingold
2008-01-30 13:19                         ` Robert Millan
2008-01-29 16:35                 ` tgingold
2008-01-30  5:48                 ` Tristan Gingold
2008-01-30 15:07                   ` Robert Millan
2008-01-30 15:33                     ` Robert Millan
2008-01-30 16:22                     ` tgingold
2008-01-30 18:38                       ` Robert Millan
2008-02-04 15:45                   ` Marco Gerards
2008-02-04 16:07                     ` Robert Millan
2008-02-05  9:51                       ` tgingold
2008-02-10 22:43                   ` Alexandre Boeglin
2008-02-11  8:59                     ` tgingold
2010-01-18 18:03                   ` Robert Millan
2008-01-30  5:48                 ` Tristan Gingold
2008-01-30  5:57                 ` Tristan Gingold
2008-01-30 13:25                   ` Robert Millan
2008-01-30 16:04                     ` tgingold
2008-03-19 17:11                       ` Robert Millan
2008-03-20  6:34                         ` Tristan Gingold
2008-02-05 22:49       ` Alexandre Boeglin
2008-01-29  5:49   ` Tristan Gingold
2008-01-29  9:08     ` Robert Millan
2008-01-29 10:10       ` tgingold
2008-01-29 11:07         ` Robert Millan
2008-01-29 12:53           ` tgingold
2008-01-29 13:39             ` Robert Millan
2008-01-29 13:36     ` 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=20080129091736.GG30048@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.