From: Ian Campbell <Ian.Campbell@citrix.com>
To: Roy Franz <roy.franz@linaro.org>
Cc: keir@xen.org, tim@xen.org, xen-devel@lists.xen.org,
stefano.stabellini@citrix.com, jbeulich@suse.com,
fu.wei@linaro.org
Subject: Re: [RFC PATCH 2/2] arm64: Create xen.efi binary for arm64
Date: Thu, 2 Oct 2014 14:03:20 +0100 [thread overview]
Message-ID: <1412255000.17146.11.camel@citrix.com> (raw)
In-Reply-To: <1412212299-13831-3-git-send-email-roy.franz@linaro.org>
On Wed, 2014-10-01 at 18:11 -0700, Roy Franz wrote:
> The 'xen' binary for arm64 is both an Image file and a PE/COFF executable,
> copy it to xen.efi so that the 'make install' processing is shared with
> x86. Prior to this 'make install' was broken on arm64.
>
> Signed-off-by: Roy Franz <roy.franz@linaro.org>
If the affect of this is only to install Xen (and some symlinks)
into /usr/lib64/efi and optionally into the ESP then:
Acked-by: Ian Campbell <ian.campbell@citrix.com>
What I don't want is for an extra xen.efi to show up in the
regular /boot directory. I think this patch doesn't do that though.
Jan, slight aside: what do you think about setting EFI_VENDOR to e.g.
XenProject by default (i.e. installing into the ESP by default)?
next prev parent reply other threads:[~2014-10-02 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 1:11 [RFC PATCH 0/2] EFI/arm64 updates Roy Franz
2014-10-02 1:11 ` [RFC PATCH 1/2] EFI: Update documentation for arm64 Roy Franz
2014-10-02 8:34 ` Jan Beulich
2014-10-02 14:10 ` Ian Campbell
2014-10-02 1:11 ` [RFC PATCH 2/2] arm64: Create xen.efi binary " Roy Franz
2014-10-02 13:03 ` Ian Campbell [this message]
2014-10-02 13:09 ` Jan Beulich
2014-10-02 14:08 ` Ian Campbell
2014-10-02 16:56 ` Roy Franz
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=1412255000.17146.11.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=fu.wei@linaro.org \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=roy.franz@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).