From: liuzhiwei <zhiwei_liu@c-sky.com>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Alistair Francis <Alistair.Francis@wdc.com>,
qemu-devel@nongnu.org,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
qemu-riscv@nongnu.org
Subject: [Qemu-devel] RISCV: when will the CLIC be ready?
Date: Fri, 16 Aug 2019 11:34:29 +0800 [thread overview]
Message-ID: <0141541d-43ff-98d8-e9d4-4a2fdcfdcf36@c-sky.com> (raw)
Hi, Palmer
When Michael Clark still was the maintainer of RISCV QEMU, he wrote in the mail list, "the CLIC interrupt controller is under testing,
and will be included in QEMU 3.1 or 3.2". It is pity that the CLIC is not in
included even in QEMU 4.1.0.
As we have cpus using CLIC, I have to use the out of tree qemu code in SIFIVE
a long time. Could you tell me when it will be upstreamed?
Best Regards
Zhiwei
WARNING: multiple messages have this Message-ID (diff)
From: liuzhiwei <zhiwei_liu@c-sky.com>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: Sagar Karandikar <sagark@eecs.berkeley.edu>,
Alistair Francis <Alistair.Francis@wdc.com>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Subject: [Qemu-riscv] RISCV: when will the CLIC be ready?
Date: Fri, 16 Aug 2019 11:34:29 +0800 [thread overview]
Message-ID: <0141541d-43ff-98d8-e9d4-4a2fdcfdcf36@c-sky.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
Hi, Palmer
When Michael Clark still was the maintainer of RISCV QEMU, he wrote in the mail list, "the CLIC interrupt controller is under testing,
and will be included in QEMU 3.1 or 3.2". It is pity that the CLIC is not in
included even in QEMU 4.1.0.
As we have cpus using CLIC, I have to use the out of tree qemu code in SIFIVE
a long time. Could you tell me when it will be upstreamed?
Best Regards
Zhiwei
[-- Attachment #2: Type: text/html, Size: 588 bytes --]
next reply other threads:[~2019-08-16 3:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 3:34 liuzhiwei [this message]
2019-08-16 3:34 ` [Qemu-riscv] RISCV: when will the CLIC be ready? liuzhiwei
2019-08-16 17:29 ` [Qemu-devel] " Alistair Francis
2019-08-16 17:29 ` [Qemu-riscv] " Alistair Francis
2019-08-19 13:39 ` liuzhiwei
2019-08-19 13:39 ` [Qemu-riscv] " liuzhiwei
2019-08-19 16:38 ` [Qemu-devel] [Qemu-riscv] " Chih-Min Chao
2019-08-19 16:38 ` [Qemu-riscv] [Qemu-devel] " Chih-Min Chao
2019-08-21 3:33 ` [Qemu-devel] [Qemu-riscv] " liuzhiwei
2019-08-21 3:33 ` [Qemu-riscv] [Qemu-devel] " liuzhiwei
2019-08-22 22:38 ` [Qemu-devel] [Qemu-riscv] " Alistair Francis
2019-08-22 22:38 ` [Qemu-riscv] [Qemu-devel] " Alistair Francis
2019-08-19 18:56 ` Alistair Francis
2019-08-19 18:56 ` [Qemu-riscv] " Alistair Francis
2019-08-20 1:21 ` Bin Meng
2019-08-20 1:21 ` [Qemu-riscv] " Bin Meng
2019-08-21 3:01 ` liuzhiwei
2019-08-21 3:01 ` [Qemu-riscv] " liuzhiwei
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=0141541d-43ff-98d8-e9d4-4a2fdcfdcf36@c-sky.com \
--to=zhiwei_liu@c-sky.com \
--cc=Alistair.Francis@wdc.com \
--cc=kbastian@mail.uni-paderborn.de \
--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: link
Be 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.