From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Bin Meng" <bin.meng@windriver.com>
Cc: qemu-stable@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
qemu-riscv@nongnu.org, Weiwei Li <liweiwei@iscas.ac.cn>,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>
Subject: [PATCH 0/2] riscv: Fix the console of the Spike machine on big endian hosts
Date: Fri, 21 Jul 2023 11:47:18 +0200 [thread overview]
Message-ID: <20230721094720.902454-1-thuth@redhat.com> (raw)
The tests/avocado/riscv_opensbi.py avocado test is currently failing
on big endian hosts since the console of the Spike machine is not
working there. With two small patches, this can be fixed: First patch
fixes riscv64, and the second one fixes riscv32.
Thomas Huth (2):
hw/char/riscv_htif: Fix printing of console characters on big endian
hosts
hw/char/riscv_htif: Fix the console syscall on big endian hosts
hw/char/riscv_htif.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
--
2.39.3
next reply other threads:[~2023-07-21 9:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 9:47 Thomas Huth [this message]
2023-07-21 9:47 ` [PATCH 1/2] hw/char/riscv_htif: Fix printing of console characters on big endian hosts Thomas Huth
2023-07-21 10:10 ` Bin Meng
2023-07-21 10:20 ` Daniel Henrique Barboza
2023-07-21 13:26 ` Philippe Mathieu-Daudé
2023-07-23 22:38 ` Alistair Francis
2023-07-21 9:47 ` [PATCH 2/2] hw/char/riscv_htif: Fix the console syscall " Thomas Huth
2023-07-21 10:10 ` Bin Meng
2023-07-21 10:20 ` Daniel Henrique Barboza
2023-07-23 22:37 ` Alistair Francis
2023-07-23 22:58 ` [PATCH 0/2] riscv: Fix the console of the Spike machine " 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=20230721094720.902454-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=liweiwei@iscas.ac.cn \
--cc=marcandre.lureau@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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 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.