From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] configs/qemu: add qemu_riscv64_virt_defconfig
Date: Wed, 5 Sep 2018 08:45:51 +0200 [thread overview]
Message-ID: <20180905084551.0e4d3e6c@windsurf> (raw)
In-Reply-To: <cd1fb718-2f8e-571e-d217-1d37ebc73b28@mind.be>
Hello,
On Tue, 4 Sep 2018 21:57:11 +0200, Arnout Vandecappelle wrote:
> On 04/09/2018 17:14, Mark Corbin wrote:
> > I had been reluctant to add riscv-pk to Buildroot as a bootloader, as I
> > see it as an interim solution until riscv support makes it into UBoot or
> > Barebox.
>
> If riscv-pk/bbl offers all the features you need, why would you use U-Boot or
> Barebox?
For the same reason that you use U-Boot or Barebox on real hardware,
rather than a completely dumb "kernel loader": shell, environment
variables, scripting, etc. I'm not saying this is always needed, but it
seems like some people like those features :-)
> > I do have a preliminary riscv-pk package working based on your helpful
> > pointers to boot-wrapper-aarch64. Do people prefer to add it as
> > 'risc-pk' when it is only the Berkeley Boot Loader part that is
> > significant? I would have added it as 'bbl', but I can see the potential
> > confusion when the package/repository is 'riscv-pk'.
>
> Unless there is some convincing reason for it, we prefer to stick with the
> upstream name.
I agree. It's true that besides the BBL, there is not much in the
riscv-pk repo that would be useful in the context of Buildroot, but
riscv-pk is just as good as riscv-bbl, and riscv-pk has the advantage
of matching the upstream name.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-09-05 6:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 14:38 [Buildroot] [PATCH 1/1] configs/qemu: add qemu_riscv64_virt_defconfig Mark Corbin
2018-08-31 19:01 ` Thomas Petazzoni
2018-09-02 15:09 ` Christopher McCrory
2018-09-04 11:06 ` Mark Corbin
2018-09-02 19:47 ` Thomas Petazzoni
2018-09-04 15:14 ` Mark Corbin
2018-09-04 19:57 ` Arnout Vandecappelle
2018-09-05 6:45 ` Thomas Petazzoni [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=20180905084551.0e4d3e6c@windsurf \
--to=thomas.petazzoni@bootlin.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 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.