From: "Keith Packard" via <qemu-devel@nongnu.org>
To: Alistair Francis <alistair23@gmail.com>
Cc: "qemu-devel\@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH 1/2] riscv: Add sifive test device to sifive_e target
Date: Fri, 23 Oct 2020 23:01:44 -0700 [thread overview]
Message-ID: <87y2jw5fhz.fsf@keithp.com> (raw)
In-Reply-To: <CAKmqyKNKAwtE6M6zSiP1mneo3GhMzz--GOjW6Yh+kaBLB=zp=g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
Alistair Francis <alistair23@gmail.com> writes:
> The sifive_u and sifive_e model real hardware (the names are confusing
> I agree) so I would rather not add a virtual device.
That seems reasonable; semihosting will be a much better solution for
the long term anyways. I posted this because we've been maintaining it
out-of-tree for several years now and I wondered if it could be merged
to reduce our ongoing qemu support costs.
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-10-24 6:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 21:45 [PATCH 0/2] riscv: Add SiFive test device to sifive targets Keith Packard via
2020-10-23 21:45 ` [PATCH 1/2] riscv: Add sifive test device to sifive_e target Keith Packard via
2020-10-23 23:38 ` Alistair Francis
2020-10-24 0:13 ` Keith Packard via
2020-10-24 0:03 ` Alistair Francis
2020-10-24 6:01 ` Keith Packard via [this message]
2020-10-23 21:45 ` [PATCH 2/2] riscv: Add sifive test device to sifive_u target Keith Packard via
2020-10-23 23:39 ` Alistair Francis
2020-10-24 0:15 ` Keith Packard via
2020-10-26 6:11 ` Bin Meng
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=87y2jw5fhz.fsf@keithp.com \
--to=qemu-devel@nongnu.org \
--cc=alistair23@gmail.com \
--cc=keithp@keithp.com \
/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).