From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] boot: riscv: Initial commit of OpenSBI
Date: Mon, 18 Mar 2019 21:46:30 +0100 [thread overview]
Message-ID: <20190318214630.5bc9ba71@windsurf> (raw)
In-Reply-To: <CAKmqyKPLkVz4nPPi_++2J=GF8n6Dzrx+RG6pZCDuhRq8oTk5LA@mail.gmail.com>
Hello,
On Mon, 18 Mar 2019 13:36:53 -0700
Alistair Francis <alistair23@gmail.com> wrote:
> > So when there's no platform defined, nothing gets installed ? This
> > looks weird.
>
> If no platform is defined then OpenSBI will just build a library that
> can be used by other projects. The idea here is to allow people to
> build that library. At the moment though nothing is using it.
OK, then you can probably keep the "build without platform" thing, but
the Config.in help text of the string option used to define the
platform should be improved to explain what happens when no platform is
defined.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-18 20:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 23:06 [Buildroot] [PATCH 1/3] arch: riscv: Add a RISC-V Platform option Alistair Francis
2019-03-15 23:06 ` [Buildroot] [PATCH 2/3] boot: riscv: Initial commit of OpenSBI Alistair Francis
2019-03-16 7:41 ` Thomas Petazzoni
2019-03-18 20:36 ` Alistair Francis
2019-03-18 20:46 ` Thomas Petazzoni [this message]
2019-03-18 21:02 ` Alistair Francis
2019-03-15 23:06 ` [Buildroot] [PATCH 3/3] boot: riscv: Remove riscv-pk Alistair Francis
2019-03-16 7:43 ` Thomas Petazzoni
2019-03-18 10:45 ` Mark Corbin
2019-03-18 17:51 ` Alistair Francis
2019-03-19 10:35 ` Mark Corbin
2019-03-18 17:46 ` Alistair Francis
2019-03-16 7:36 ` [Buildroot] [PATCH 1/3] arch: riscv: Add a RISC-V Platform option Thomas Petazzoni
2019-03-18 20:30 ` Alistair Francis
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=20190318214630.5bc9ba71@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox