qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] target description XML support for PowerPC
Date: Sat, 24 Jan 2009 16:09:12 +0100	[thread overview]
Message-ID: <20090124150912.GY19498@hall.aurel32.net> (raw)
In-Reply-To: <1232656933-28425-1-git-send-email-froydnj@codesourcery.com>

On Thu, Jan 22, 2009 at 12:42:07PM -0800, Nathan Froyd wrote:
> This patch series implements target description XML support for PowerPC
> in the GDB stub.  It's fairly straightforward:
> 
> - Include the necessary XML files in the build process;
> - Inform the GDB stub that we have XML for PowerPC;
> - Instruct the stub on how to use the XML files for the three major
>   flavors of "extra" registers: floating-point, AltiVec, and SPE.
> 
> Ideally, support can be added later for sending interesting SPRs.
> 

Thanks, applied with minor warning fixes in patch 6.


-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

      parent reply	other threads:[~2009-01-24 15:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 20:42 [Qemu-devel] [PATCH 0/6] target description XML support for PowerPC Nathan Froyd
2009-01-22 20:42 ` [Qemu-devel] [PATCH 1/6] Add XML files for PowerPC registers Nathan Froyd
2009-01-22 20:42 ` [Qemu-devel] [PATCH 2/6] Change core powerpc gdbstub bits to be XML-aware Nathan Froyd
2009-01-22 20:42 ` [Qemu-devel] [PATCH 3/6] Include gdbstub.h Nathan Froyd
2009-01-22 20:42 ` [Qemu-devel] [PATCH 4/6] Add float register read/write using XML Nathan Froyd
2009-01-22 20:42 ` [Qemu-devel] [PATCH 5/6] Add Altivec " Nathan Froyd
2009-01-22 20:42 ` [Qemu-devel] [PATCH 6/6] Add SPE " Nathan Froyd
2009-01-24 15:09 ` Aurelien Jarno [this message]

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=20090124150912.GY19498@hall.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=froydnj@codesourcery.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).