From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Kernel fixes for Cygwin
Date: Mon, 21 Jul 2008 13:03:26 -0400 [thread overview]
Message-ID: <1216659806.3460.61.camel@dv> (raw)
In-Reply-To: <1216659036.3033.10.camel@localhost>
On Mon, 2008-07-21 at 18:50 +0200, Javier Martín wrote:
> Of course, another way to go could be to allow the bootloader part of
> GRUB to be built in PE format: it would "just" be a matter of writing
> the PE counterparts to kern/elf.c and abstracting kern/dl.c "a
> bit" (i.e. a lot of work). The downside to this, apart from the
> unspecified work required, is that Windows-built i386-pc-pe modules are
> no longer compatible with Linux-built i386-pc-elf. Not a showstopper,
> but might require a sober thinking. As I have a lot of free time right
> now, I'll try to think whether it's possible or not.
I think it's important to have a consistent format for modules.
> > Maybe we could treat ELF header like a multiboot header? That means
> > that we write the header fields in the assembly language, substitute the
> > necessary variables and ask objcopy to make a raw binary that would
> > actually be an ELF file?
> As far as I understand the ELF format, this would be too complex to get
> right: there's a lot of info in there.
If ELF is too complex to write manually, we can use another format
everywhere. It could be something GRUB specific. But I think we should
try to use ELF, as it's widespread and extensible.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-07-21 17:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 20:51 [PATCH] Kernel fixes for Cygwin Christian Franke
2008-07-21 7:02 ` Bean
2008-07-21 7:25 ` Bean
2008-07-21 10:33 ` Christian Franke
2008-07-21 10:56 ` Bean
2008-07-22 16:58 ` Christian Franke
2008-07-21 11:02 ` Javier Martín
2008-07-21 11:16 ` Christian Franke
2008-07-21 15:51 ` Pavel Roskin
2008-07-21 16:50 ` Javier Martín
2008-07-21 17:03 ` Pavel Roskin [this message]
2008-07-21 17:23 ` Javier Martín
2008-07-21 19:59 ` Pavel Roskin
2008-07-21 10:21 ` Christian Franke
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=1216659806.3460.61.camel@dv \
--to=proski@gnu.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.