All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@penguinppc.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multiboot2: make multiboot header optional
Date: Tue, 21 Nov 2006 10:18:48 -0600	[thread overview]
Message-ID: <1164125928.29331.24.camel@basalt> (raw)
In-Reply-To: <1163634117.455ba5c54cab9@imp8-g19.free.fr>

On Thu, 2006-11-16 at 00:41 +0100, tgingold@free.fr wrote:
> Quoting "Yoshinori K. Okuji" <okuji@enbug.org>:
> 
> > On Tuesday 14 November 2006 23:58, Hollis Blanchard wrote:
> > > I would like to make the in-kernel multiboot header optional. If it's an
> > > ELF file, we can load it, even if it doesn't have the header. We can
> > > also pass the address of the multiboot tags to its entry point (it can't
> > > hurt anything).
> >
> > I prefer to keep a multiboot header, because GRUB may not detect an error
> > that the offset of a multiboot header is beyond 8192 bytes.
> BTW, on ia64 8192 is too small.  Linux and Xen put the ivt (interrupt vector
> table) at the head of the file because it has the largest alignment
> requirement (32Kb).  I am not sure there is a big enough hole in the ivt.
> And Xen has two ivt (-> 64kB).
> However both Linux and Xen use the ELF format.

Do you have a proposal to solve this problem? Are you advocating
dropping the multiboot header, since we can load ELF files without it?

-Hollis




  reply	other threads:[~2006-11-21 16:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 22:58 multiboot2: make multiboot header optional Hollis Blanchard
2006-11-15  8:57 ` Johan Rydberg
2006-11-15 18:42   ` Hollis Blanchard
2006-11-15 20:42     ` Yoshinori K. Okuji
2006-11-15 21:39       ` Hollis Blanchard
2006-11-15 23:38         ` tgingold
2006-11-25  2:59           ` Yoshinori K. Okuji
2006-11-25  3:35             ` Hollis Blanchard
2006-11-25  4:25               ` Yoshinori K. Okuji
2006-12-02 16:18                 ` Marco Gerards
2006-12-02 17:27                   ` Yoshinori K. Okuji
2006-12-04 16:43                     ` Hollis Blanchard
2006-12-05 20:23                       ` Yoshinori K. Okuji
2006-12-07 23:07                         ` multiboot2: using tags in the multiboot header Hollis Blanchard
2006-12-12 22:23                           ` Yoshinori K. Okuji
2006-12-04 20:35                     ` multiboot2: make multiboot header optional Marco Gerards
2006-12-05 19:09                       ` Hollis Blanchard
2006-12-05 20:04                         ` Yoshinori K. Okuji
2006-12-07 22:39                           ` Hollis Blanchard
2006-12-12 22:08                             ` Yoshinori K. Okuji
2006-12-13  4:18                               ` Hollis Blanchard
2006-12-13 20:56                                 ` Yoshinori K. Okuji
2006-12-13 12:28                         ` Marco Gerards
2006-12-02 16:15       ` Marco Gerards
2006-12-02 17:19         ` Yoshinori K. Okuji
2006-11-15 20:37 ` Yoshinori K. Okuji
2006-11-15 23:41   ` tgingold
2006-11-21 16:18     ` Hollis Blanchard [this message]
2006-11-21 17:35       ` tgingold
2006-11-25  3:05         ` Yoshinori K. Okuji
2006-11-25  3:00     ` Yoshinori K. Okuji
2006-11-25  6:12       ` Tristan Gingold

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=1164125928.29331.24.camel@basalt \
    --to=hollis@penguinppc.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.