From: Joe Komlodi <joe.komlodi@xilinx.com>
To: qemu-devel@nongnu.org
Cc: edgar.iglesias@xilinx.com
Subject: [PATCH v1 0/1] target/microblaze: Add GDB XML files
Date: Thu, 21 May 2020 21:02:14 -0700 [thread overview]
Message-ID: <1590120134-39470-2-git-send-email-komlodi@xilinx.com> (raw)
In-Reply-To: <1590120134-39470-1-git-send-email-komlodi@xilinx.com>
Hi all,
This adds GDB XML files for Microblaze CPUs.
For Microblaze, it's split up into core and stack protect XML files.
Thanks!
Joe
Joe Komlodi (1):
target/microblaze: Add GDB XML files for Microblaze
configure | 1 +
gdb-xml/microblaze-core.xml | 62 ++++++++++++++++++++++++++++++++++++
gdb-xml/microblaze-stack-protect.xml | 12 +++++++
target/microblaze/cpu.c | 1 +
4 files changed, 76 insertions(+)
create mode 100644 gdb-xml/microblaze-core.xml
create mode 100644 gdb-xml/microblaze-stack-protect.xml
--
2.7.4
next prev parent reply other threads:[~2020-05-22 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 4:02 [PATCH v1 1/1] target/microblaze: Add GDB XML files for Microblaze Joe Komlodi
2020-05-22 4:02 ` Joe Komlodi [this message]
2020-05-22 7:14 ` [PATCH v1 0/1] target/microblaze: Add GDB XML files Edgar E. Iglesias
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=1590120134-39470-2-git-send-email-komlodi@xilinx.com \
--to=joe.komlodi@xilinx.com \
--cc=edgar.iglesias@xilinx.com \
--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).