From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Daniel Kiper <dkiper@net-space.pl>,
The development of GNU GRUB <grub-devel@gnu.org>
Cc: phcoder@gmail.com, daniel.kiper@oracle.com
Subject: Re: grub-lnstall option (UEFI) for chainloading
Date: Mon, 12 Oct 2015 23:08:24 +0300 [thread overview]
Message-ID: <561C1338.8050301@gmail.com> (raw)
In-Reply-To: <20151012163939.GA17235@router-fw-old.local.net-space.pl>
12.10.2015 19:39, Daniel Kiper пишет:
> On Mon, Oct 12, 2015 at 12:31:54PM +0300, Andrei Borzenkov wrote:
>> On Tue, Sep 8, 2015 at 12:39 AM, Barry Jackson <zen25000@zen.co.uk> wrote:
>>> On 06/06/15 09:38, Andrei Borzenkov wrote:
>>>>
>>>> ?? Fri, 05 Jun 2015 14:56:20 +0100
>>>> Barry Jackson <zen25000@zen.co.uk> ??????????:
>>>
>>>
>>>>> Any progress on this?
>>>>>
>>>>
>>>>
>>>> Not really, sorry. Do you have any suggestion how such option should be
>>>> named?
>>>>
>>>
>>> Sorry for delay - this got lost in the noise.
>>>
>>> Well something like --no-id-or-nvram ??
>>>
>>> Not really bothered about the name! :)
>>
>> I was about to suggest a patch when I realized that this probably is
>> currently useless on EFI. I.e. to actually chainload grub on EFI it
>> must reside on a partition accessible by firmware which practically
>> means it should be ESP.
>>
>> Unless someone submits patch to make grub2 EFI core.img multiboot2
>> compliant with tag to skip ExitBootServices.
>
> Relevant patches waiting for review for months. I am working on v3.
> If they are upstreamed I will be happy too.
>
Your patches implement "client side" support (loading MB2 images); but
EFI grub is not MB2 and has no provision for being loaded this way. Also
it is PE, not ELF.
Actually chainloading probably could be made to work on arbitrary
filesystem if argument parsing is added (to pass along cmdpath).
next prev parent reply other threads:[~2015-10-12 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 12:11 grub-lnstall option (UEFI) for chainloading Barry Jackson
2015-03-29 13:12 ` Andrei Borzenkov
2015-03-30 9:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-03-30 9:58 ` Andrei Borzenkov
2015-06-05 13:56 ` Barry Jackson
2015-06-06 8:38 ` Andrei Borzenkov
2015-09-07 21:39 ` Barry Jackson
2015-10-12 9:31 ` Andrei Borzenkov
2015-10-12 16:39 ` Daniel Kiper
2015-10-12 20:08 ` Andrei Borzenkov [this message]
2015-10-12 20:59 ` Daniel Kiper
2016-06-06 11:20 ` Barry Jackson
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=561C1338.8050301@gmail.com \
--to=arvidjaar@gmail.com \
--cc=daniel.kiper@oracle.com \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.com \
/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).