From: David Brenken <david.brenken@efs-auto.org>
To: qemu-devel@nongnu.org
Cc: kbastian@mail.uni-paderborn.de,
David Brenken <david.brenken@efs-auto.de>
Subject: [Qemu-devel] [PATCH 0/5] tricore: added small features + fixed wrong masks
Date: Mon, 19 Feb 2018 07:18:22 +0100 [thread overview]
Message-ID: <20180219061827.2112-1-david.brenken@efs-auto.org> (raw)
From: David Brenken <david.brenken@efs-auto.de>
Hello,
this is my first commit of a patch set for QEMU.
This patch series contains a few updates for the target tricore:
- adding a few additional, previously missing cpu instructions
- adding CORE_ID
- fixing some masks
- fixing a wrong shift (context PCXI PIE)
David Brenken (5):
tricore: added some missing cpu instructions
tricore: added CORE_ID
tricore: fixed wrong masking of IE
tricore: fixed wrong mask of PCXI_PIE
tricore: fixed wrong shifting of PCXI PIE
target/tricore/cpu.h | 5 +++--
target/tricore/csfr.def | 1 +
target/tricore/op_helper.c | 3 ++-
target/tricore/translate.c | 22 ++++++++++++++++++++++
target/tricore/tricore-opcodes.h | 4 ++++
5 files changed, 32 insertions(+), 3 deletions(-)
--
2.7.4
next reply other threads:[~2018-02-19 6:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 6:18 David Brenken [this message]
2018-02-19 6:18 ` [Qemu-devel] [PATCH 1/5] tricore: added some missing cpu instructions David Brenken
2018-02-20 15:48 ` Bastian Koppelmann
2018-02-19 6:18 ` [Qemu-devel] [PATCH 2/5] tricore: added CORE_ID David Brenken
2018-02-20 15:53 ` Bastian Koppelmann
2018-02-19 6:18 ` [Qemu-devel] [PATCH 3/5] tricore: fixed wrong masking of IE David Brenken
2018-02-20 15:59 ` Bastian Koppelmann
2018-02-19 6:18 ` [Qemu-devel] [PATCH 4/5] tricore: fixed wrong mask of PCXI_PIE David Brenken
2018-02-20 16:03 ` Bastian Koppelmann
2018-02-19 6:18 ` [Qemu-devel] [PATCH 5/5] tricore: fixed wrong shifting of PCXI PIE David Brenken
2018-02-20 15:48 ` [Qemu-devel] [PATCH 0/5] tricore: added small features + fixed wrong masks Bastian Koppelmann
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=20180219061827.2112-1-david.brenken@efs-auto.org \
--to=david.brenken@efs-auto.org \
--cc=david.brenken@efs-auto.de \
--cc=kbastian@mail.uni-paderborn.de \
--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).