All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] ELF64 and changelog and 4Gb
Date: Thu, 21 Jul 2005 23:51:48 +0200	[thread overview]
Message-ID: <87br4v6d57.fsf@student.han.nl> (raw)
In-Reply-To: <20050719230122.F19A64BEAD@ws1-1.us4.outblaze.com> (Ruslan Nikolaev's message of "Tue, 19 Jul 2005 18:01:22 -0500")

"Ruslan Nikolaev" <nruslan@mail.com> writes:

>> I agree. This is more readable.
>
> I can change it of course... But it is not so bad:
>
> 1. if elf class == 64 => using ELF64 validate & loading code
>
> 2. else:
>
> - validate header by grub_dl_check_header(). Function
> grub_dl_check_header() also will check that elf class is 32-bit.

The important thing to remember is that GRUB support more machines
than the PC and other loaders than just multiboot.  So having a ELF32
and ELF64 loader like Hollis suggested would be the right thing to
do.  It will mean more shared code and a clean solution.

Thanks,
Marco




      parent reply	other threads:[~2005-07-21 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 23:01 [PATCH] ELF64 and changelog and 4Gb Ruslan Nikolaev
2005-07-20 20:50 ` Yoshinori K. Okuji
2005-07-21 21:51 ` Marco Gerards [this message]

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=87br4v6d57.fsf@student.han.nl \
    --to=metgerards@student.han.nl \
    --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.