From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Fwd: Is grub-bios-setup the way to go to make a bootable CF?
Date: Sat, 4 Nov 2017 18:45:14 +0100 [thread overview]
Message-ID: <5b6d5829-7621-3efa-96bc-65db27ae7ef4@mind.be> (raw)
In-Reply-To: <CACznjzK_AA_p348WfNZ9DTBtH0c+Qv3p3su4jAFAhN8NGuXX=g@mail.gmail.com>
On 03-11-17 22:23, Andr?s Fern?ndez wrote:
> Hello BR people.
>
> ?
>
> I have exactly the same problem described in this e-mail list:
> http://lists.busybox.net/pipermail/buildroot/2014-June/100652.html
> <http://lists.busybox.net/pipermail/buildroot/2014-June/100652.html>
>
> Have these issue any solution?
This should have been fixed by commit 8a5a57de1c8f8eec9c49b53846e23a64bf251d9d
and setting BR2_TARGET_GRUB2_BOOT_PARTITION to the correct partition. However,
the original poster never confirmed that it solved the situation for him.
Could you explain in detail what is not working for you, and how you configured
your system?
Regards,
Arnout
>
> ?
>
> BR,
>
> Andr?s Fern?ndez
>
> CRC
>
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2017-11-04 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACznjz+wnkYCFfzYph7=N7QvS=WRznT8RHXXDTmoVeULkzDL+w@mail.gmail.com>
2017-11-03 21:23 ` [Buildroot] Fwd: Is grub-bios-setup the way to go to make a bootable CF? Andrés Fernández
2017-11-04 17:45 ` Arnout Vandecappelle [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=5b6d5829-7621-3efa-96bc-65db27ae7ef4@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.