From: Max Filippov <jcmvbkbc@gmail.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: [Qemu-devel] [PULL v2 0/4] target/xtensa fixes
Date: Tue, 6 Jun 2017 03:52:09 -0700 [thread overview]
Message-ID: <1496746329-32047-1-git-send-email-jcmvbkbc@gmail.com> (raw)
Hi Peter,
please pull my current target/xtensa queue.
Changes v1->v2:
- re-base series to the latest mainline, fixing breakage caused by chardev
code rearrangement.
The following changes since commit a0d4aac7467dd02e5657b79e867f067330266a24:
Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20170605' into staging (2017-06-05 18:03:43 +0100)
are available in the git repository at:
git://github.com/OSLL/qemu-xtensa.git tags/20170606-xtensa
for you to fetch changes up to dd7b952b793e341c905355581a21cdbaa8b13c31:
target/xtensa: handle unknown registers in gdbstub (2017-06-06 02:40:48 -0700)
----------------------------------------------------------------
target/xtensa fixes:
- fix read/write simcall mapping flags and return value;
- use -serial option to direct console output of sim machine to QEMU chardev;
- fix handling of unknown registers in the gdbstub.
----------------------------------------------------------------
Max Filippov (4):
target/xtensa: fix mapping direction in read/write simcalls
target/xtensa: fix return value of read/write simcalls
target/xtensa: support output to chardev console
target/xtensa: handle unknown registers in gdbstub
hw/xtensa/sim.c | 4 ++
target/xtensa/cpu.h | 1 +
target/xtensa/gdbstub.c | 13 +++++--
target/xtensa/xtensa-semi.c | 91 +++++++++++++++++++++++++++++++++++----------
4 files changed, 87 insertions(+), 22 deletions(-)
--
Thanks.
-- Max
next reply other threads:[~2017-06-06 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 10:52 Max Filippov [this message]
2017-06-06 17:34 ` [Qemu-devel] [PULL v2 0/4] target/xtensa fixes Peter Maydell
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=1496746329-32047-1-git-send-email-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=peter.maydell@linaro.org \
--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).