From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Add linuxefi module
Date: Tue, 21 Jan 2014 14:53:36 +0100 [thread overview]
Message-ID: <52DE7BE0.8090702@gmail.com> (raw)
In-Reply-To: <20140121134357.GA11502@riva.ucam.org>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On 21.01.2014 14:43, Colin Watson wrote:
> I would be inclined to say that linuxefi should be essentially an
> internal implementation detail, and that linux should forward to
> linuxefi if appropriate.
Current 32-bit protocol is very useful on platforms like coreboot.
Removing its use in GRUB combined with Linux devs like hpa who are
hostile to coreboot (and blocked introduction of 32-bit interface for
years until bowing to EFI), I fear that 32-bit entry point might become
unusable very quickly.
Speaking of quirk handling, when I asked about mjg details he was very
vague and details are important.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 274 bytes --]
next prev parent reply other threads:[~2014-01-21 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 23:28 [PATCH] Add linuxefi module Lubomir Rintel
2014-01-21 1:46 ` SevenBits
2014-01-21 13:43 ` Colin Watson
2014-01-21 13:53 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2014-01-21 15:24 ` SevenBits
2014-01-21 16:24 ` Andrey Borzenkov
2014-01-21 16:29 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-01-21 23:29 ` Colin Watson
2014-01-22 15:00 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-01-21 16:30 ` Matthew Garrett
2014-01-21 19:20 ` Leif Lindholm
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=52DE7BE0.8090702@gmail.com \
--to=phcoder@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).