All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tristan Gingold <tgingold@free.fr>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multiboot2: remove "a.out kludge" requirement
Date: Sun, 19 Nov 2006 17:55:07 +0100	[thread overview]
Message-ID: <20061119165507.GA2854@saphi> (raw)
In-Reply-To: <3a73d3420611190226k23254d59vd3e6acb189a585be@mail.gmail.com>

On Sun, Nov 19, 2006 at 10:26:54AM +0000, Brano Zarnovican wrote:
> On 11/17/06, Andrei E. Warkentin <andrey.warkentin@gmail.com> wrote:
> >
> >How about having a custom e_type for ELF images booted by GRUB? Something 
> >in
> 
> Guys at Xen solved it nicely with custom ELF section. Somewhere in
> your OS code you create a section with specific name, bootloader will
> be looking for. For multiboot it might look like:
> 
> .section __multiboot_v2
>        .long MAGIC_THIS
>        .long FLAGS_THAT
> 
> Header position is exactly defined in ELF which Grub already speaks.
> It does not need to be in first 8kB. The downside is that it will make
> multiboot ELF-only.
> 
> Oh. Did I mention that you can have more than one header in a single image ?
> (for non-compatible multiboot versions ;)
But using notes make it almost impossible to use a compressed image.
(This is almost a requirement for ia64, but I also think ia64 does not
require these flags).

Tristan.




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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 21:10 multiboot2: remove "a.out kludge" requirement Hollis Blanchard
2006-11-17 21:27 ` Andrei E. Warkentin
2006-11-17 22:01   ` Hollis Blanchard
2006-11-17 22:36     ` Andrei E. Warkentin
2006-11-18  0:32       ` Hollis Blanchard
2006-11-19 10:26   ` Brano Zarnovican
2006-11-19 16:55     ` Tristan Gingold [this message]
2006-11-19 19:31       ` Andrei E. Warkentin
2006-11-19 19:58         ` Tristan Gingold
2006-11-20 19:13       ` Hollis Blanchard
2006-11-20 20:24         ` Tristan Gingold
2006-11-20 19:14     ` Hollis Blanchard
2006-11-25  3:01 ` Yoshinori K. Okuji

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=20061119165507.GA2854@saphi \
    --to=tgingold@free.fr \
    --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.