From: Alistair Francis <alistair23@gmail.com> To: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org> Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>, Sagar Karandikar <sagark@eecs.berkeley.edu>, onathan@fintelia.io, Bastian Koppelmann <kbastian@mail.uni-paderborn.de>, Palmer Dabbelt <palmer@sifive.com>, Alistair Francis <Alistair.Francis@wdc.com> Subject: [Qemu-devel] RISC-V: Include ROM in QEMU Date: Thu, 6 Jun 2019 16:22:47 -0700 [thread overview] Message-ID: <CAKmqyKMs4nt0eddFkXHG9vOdxnj=yB8jx8s9NivNiwvVg8TObA@mail.gmail.com> (raw) 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. Alistair
WARNING: multiple messages have this Message-ID (diff)
From: Alistair Francis <alistair23@gmail.com> To: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org> Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>, Sagar Karandikar <sagark@eecs.berkeley.edu>, Bastian Koppelmann <kbastian@mail.uni-paderborn.de>, Palmer Dabbelt <palmer@sifive.com>, Alistair Francis <Alistair.Francis@wdc.com>, onathan@fintelia.io Subject: [Qemu-riscv] RISC-V: Include ROM in QEMU Date: Thu, 6 Jun 2019 16:22:47 -0700 [thread overview] Message-ID: <CAKmqyKMs4nt0eddFkXHG9vOdxnj=yB8jx8s9NivNiwvVg8TObA@mail.gmail.com> (raw) 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. Alistair
next reply other threads:[~2019-06-06 23:26 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-06 23:22 Alistair Francis [this message] 2019-06-06 23:22 ` [Qemu-riscv] RISC-V: Include ROM in QEMU Alistair Francis 2019-06-08 0:03 ` [Qemu-devel] " Palmer Dabbelt 2019-06-08 0:03 ` [Qemu-riscv] " Palmer Dabbelt 2019-06-11 6:30 ` [Qemu-devel] " Gerd Hoffmann 2019-06-11 6:30 ` [Qemu-riscv] " Gerd Hoffmann 2019-06-18 22:17 ` Alistair Francis 2019-06-18 22:17 ` [Qemu-riscv] " Alistair Francis 2019-06-19 14:27 ` Alistair Francis 2019-06-19 14:27 ` [Qemu-riscv] " Alistair Francis 2019-06-18 22:17 ` Alistair Francis 2019-06-18 22:17 ` [Qemu-riscv] " 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='CAKmqyKMs4nt0eddFkXHG9vOdxnj=yB8jx8s9NivNiwvVg8TObA@mail.gmail.com' \ --to=alistair23@gmail.com \ --cc=Alistair.Francis@wdc.com \ --cc=kbastian@mail.uni-paderborn.de \ --cc=onathan@fintelia.io \ --cc=palmer@sifive.com \ --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: linkBe 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.