From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] build 32-bit Linux loader as `linux', rename legacy loader to `linux16'
Date: Wed, 01 Apr 2009 10:04:44 -0400 [thread overview]
Message-ID: <1238594684.32385.6.camel@mj> (raw)
In-Reply-To: <20090401132322.GE27958@thorin>
On Wed, 2009-04-01 at 15:23 +0200, Robert Millan wrote:
> On Mon, Mar 30, 2009 at 05:51:22PM -0400, Pavel Roskin wrote:
> >
> > If we are circumventing the standard Linux bootloader, perhaps we should
> > communicate this to the Linux developers.
>
> This is not circumvention. We're using a 32-bit interface that's part of their
> boot protocol specification (i.e. they promised not to break it). The only
> caveat is that so far it's only used on EFI and on coreboot, it hasn't been
> so widespread, and therefore not so widely tested yet.
I see. It looks like the x86_64 kernel has code for printing strings in
16-bit mode and in 64-bit mode, but not in 32-bit mode, in which we
enter the kernel. So no easy fix, unfortunately.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-04-01 14:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 19:57 [PATCH] linux/gfxterm integration Robert Millan
2009-03-08 13:01 ` Robert Millan
2009-03-08 13:09 ` Robert Millan
2009-03-08 13:35 ` Vesa Jääskeläinen
2009-03-13 19:44 ` Robert Millan
2009-03-13 20:10 ` David Miller
2009-03-18 10:25 ` new Linux loader (Re: [PATCH] linux/gfxterm integration) Robert Millan
2009-03-18 13:09 ` phcoder
2009-03-21 17:50 ` Robert Millan
2009-03-22 16:00 ` [PATCH] build 32-bit Linux loader as `linux', rename legacy loader to `linux16' Robert Millan
2009-03-28 12:53 ` Robert Millan
2009-03-30 13:32 ` Pavel Roskin
2009-03-30 14:35 ` phcoder
2009-03-30 16:06 ` Yoshinori K. Okuji
2009-03-30 21:51 ` Pavel Roskin
2009-04-01 13:23 ` Robert Millan
2009-04-01 14:04 ` Pavel Roskin [this message]
2009-04-01 14:22 ` Robert Millan
2009-04-01 13:33 ` 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=1238594684.32385.6.camel@mj \
--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.