Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fs/iso9660: doesn't support (grub2) EFI
Date: Thu, 02 Mar 2017 08:20:54 +0100	[thread overview]
Message-ID: <87bmtkgn55.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170301215400.5f184cac@free-electrons.com> (Thomas Petazzoni's message of "Wed, 1 Mar 2017 21:54:00 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > Hello,
 > On Wed, 1 Mar 2017 21:05:42 +0100, Arnout Vandecappelle
 > (Essensium/Mind) wrote:
 >> The iso9660 generation for grub2 assumes that grub-eltorito.img is
 >> available. However, this image is only available for the i386-pc target
 >> (i.e. legacy BIOS). An EFI-bootable iso9660 requires a different layout.
 >> 
 >> Since we currently can't generate the EFI-bootable iso9660 layout,
 >> require the i386-pc target to be selected in grub.
 >> 
 >> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
 >> Reported-by: arnaud.miche at orange.com
 >> ---
 >> fs/iso9660/Config.in | 8 ++++----
 >> 1 file changed, 4 insertions(+), 4 deletions(-)

 > Applied to master, thanks. Peter, I believe this one qualifies for the
 > LTS branch.

Committed to 2017.02.x, thanks.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2017-03-02  7:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 17:14 [Buildroot] fs/iso9660, grub2 : grub-eltorito.img not found during the generation of rootfs.iso9660 arnaud.miche at orange.com
2017-03-01 19:59 ` Arnout Vandecappelle
2017-03-01 20:05   ` [Buildroot] [PATCH] fs/iso9660: doesn't support (grub2) EFI Arnout Vandecappelle
2017-03-01 20:21     ` Yann E. MORIN
2017-03-01 20:54     ` Thomas Petazzoni
2017-03-02  7:20       ` Peter Korsgaard [this message]

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=87bmtkgn55.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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