From: Programmingkid <programmingkidx@gmail.com>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: alistair23@gmail.com, alistair.francis@wdc.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RISC-V platform
Date: Thu, 2 Aug 2018 19:59:17 -0400 [thread overview]
Message-ID: <8CD3DD6C-8FE0-4D25-884C-E2CCFEC5E0B4@gmail.com> (raw)
In-Reply-To: <mhng-7a78b931-d225-4006-bbc7-707c9d471ef0@palmer-si-x1c4>
> On Aug 2, 2018, at 5:07 PM, Palmer Dabbelt <palmer@sifive.com> wrote:
>
> On Fri, 29 Jun 2018 14:20:34 PDT (-0700), alistair23@gmail.com wrote:
>> On Fri, Jun 29, 2018 at 2:05 PM, G 3 <programmingkidx@gmail.com> wrote:
>>> Hi, I noticed your RISC-V patches on the mailing list and had a question
>>> that I think you may be able to answer. Has anyone defined a RISC-V platform
>>> yet? What I mean is defining what devices would be found on a RISC-V
>>> motherboard. I do hope to see RISC-V based desktop systems one day. But
>>> before that day can come the platform for this chip would have to be
>>> established. Could the SiFive board be the basis for such a standard?
>>
>> It really depends what you mean by a standard platform. At the moment
>> the SiFive HiFive Unleased board is the only ASIC that can boot Linux.
>> So that really is the "standard" RISC-V board. It is a pretty basic
>> embedded board though, so it can't be considered a "standard" RISC-V
>> desktop. There is a virt board in QEMU (which is similar to the HiFive
>> Unleashed) that is a good go to for QEMU work.
>
> The HiFive Unleashed is the defacto standard RISC-V embedded Linux platform right now, but there will be a RISC-V platform specification that defines proper standard platforms of various types. This effort hasn't been started yet, but it should be done sooner rather than later.
I definitely agree it should come soon. I realize the QEMU community could start this effort rather easily by developing a machine and then porting software to it. I'm thinking something easy we could do is take the IBM PC standard and apply it with a RISC-V CPU. Hardware vendors could then take that emulated machine and turn it into a real machine. Linux distros could then be made to run on this platform. The future looks exciting for this CPU.
prev parent reply other threads:[~2018-08-02 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 21:05 [Qemu-devel] RISC-V platform G 3
2018-06-29 21:20 ` Alistair Francis
2018-08-02 21:07 ` Palmer Dabbelt
2018-08-02 23:59 ` Programmingkid [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=8CD3DD6C-8FE0-4D25-884C-E2CCFEC5E0B4@gmail.com \
--to=programmingkidx@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=palmer@sifive.com \
--cc=qemu-devel@nongnu.org \
/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).