From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11841] New: grub-efi.cfg not used when building EFI disk image
Date: Sat, 04 May 2019 04:48:55 +0000 [thread overview]
Message-ID: <bug-11841-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11841
Bug ID: 11841
Summary: grub-efi.cfg not used when building EFI disk image
Product: buildroot
Version: 2019.02.2
Hardware: All
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: pmorici at dev295.com
CC: buildroot at uclibc.org
Target Milestone: ---
In the board/pc directory there is a file grub-efi.cfg that the readme.txt file
says is used when building an EFI based image but it doesn't appear that the
grub configuration from that file is ever used any place. Instead, the script
post-image-efi-gpt.sh has a grub configuration embedded in it that gets used.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-05-04 4:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 4:48 bugzilla at busybox.net [this message]
2019-05-10 7:39 ` [Buildroot] [Bug 11841] grub-efi.cfg not used when building EFI disk image bugzilla at busybox.net
2019-05-15 20:41 ` bugzilla at busybox.net
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=bug-11841-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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