From: Palmer Dabbelt <palmer@sifive.com>
To: alistair23@gmail.com
Cc: qemu-riscv@nongnu.org, sagark@eecs.berkeley.edu,
onathan@fintelia.io,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
qemu-devel@nongnu.org,
Alistair Francis <Alistair.Francis@wdc.com>
Subject: Re: [Qemu-devel] RISC-V: Include ROM in QEMU
Date: Fri, 07 Jun 2019 17:03:42 -0700 (PDT) [thread overview]
Message-ID: <mhng-03d5c9ed-4818-4efc-99e0-cdceab2eab3d@palmer-si-x1e> (raw)
In-Reply-To: <CAKmqyKMs4nt0eddFkXHG9vOdxnj=yB8jx8s9NivNiwvVg8TObA@mail.gmail.com>
On Thu, 06 Jun 2019 16:22:47 PDT (-0700), alistair23@gmail.com wrote:
> Hello,
>
> As a test of the waters, how would the QEMU community feel about
> including the RISC-V OpenSBI project as a ROM submodule?
>
> The idea would be to have OpenSBI (similar to ATF for ARM and a BIOS
> for x86) included by default to simplify the QEMU RISC-V boot process
> for users. This would remove the requirement for users/developers to
> build a RISC-V firmware. The goal here is to allow people to just
> download and run their kernel as easily as they currently do for x86.
>
> We would make sure that it can be disabled! That is users/developers
> can use their own (or none) if they want to. The idea here is just to
> simplify the boot process, not lock anyone out.
I like it. My only question is about the mechanics of doing so: are we just
going to assume there's a cross compiler in PATH? I guess that's less of a
usability headache than needing a complier and a firmware.
next prev parent reply other threads:[~2019-06-08 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 23:22 [Qemu-devel] RISC-V: Include ROM in QEMU Alistair Francis
2019-06-08 0:03 ` Palmer Dabbelt [this message]
2019-06-11 6:30 ` Gerd Hoffmann
2019-06-18 22:17 ` Alistair Francis
2019-06-19 14:27 ` Alistair Francis
2019-06-18 22:17 ` 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=mhng-03d5c9ed-4818-4efc-99e0-cdceab2eab3d@palmer-si-x1e \
--to=palmer@sifive.com \
--cc=Alistair.Francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=onathan@fintelia.io \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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;
as well as URLs for NNTP newsgroup(s).