qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "François Revol" <revol@free.fr>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] [RFC] PPC: dump DCRs from monitor
Date: Wed, 29 Aug 2012 19:43:49 +0200	[thread overview]
Message-ID: <503E54D5.1070201@free.fr> (raw)
In-Reply-To: <8B4B40DA-1F9B-4B38-8D59-1A421B11B98E@suse.de>

On 29/08/2012 16:53, Alexander Graf wrote:
> 
> 
> On 29.08.2012, at 04:03, François Revol <revol@free.fr> wrote:
> 
>> Hi,
>> I noticed the DCRs weren't shown with the registers or another command,
>> and tried to add one to dump them to help debugging my sam460ex target.
>> This first version doesn't list the names since they aren't registered
>> as such.
>> I tried adding a name arg to ppc_dcr_register, and a #define to get it
>> from the index, but it seems some code uses a loop to register them, so
>> it gives a dump like:
>> DCR[SDRAM0_CFGDATA 11]    00000000
>> DCR[dcr_base + i c0]    00000000
>> DCR[dcr_base + i c1]    00000000
>> Any suggestion?
>> BTW, they aren't saved in state dumps, are they?
> 
> Are they accessible through the monitor's p command? Would be good to implement there too if not.

I don't think so, which syntax would you use anyway? $dcr[n] ?


François.

  reply	other threads:[~2012-08-29 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 11:03 [Qemu-devel] [PATCH] [RFC] PPC: dump DCRs from monitor François Revol
2012-08-29 14:53 ` Alexander Graf
2012-08-29 17:43   ` François Revol [this message]
2012-08-29 17:55     ` Alexander Graf
2012-08-30 10:01       ` François Revol

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=503E54D5.1070201@free.fr \
    --to=revol@free.fr \
    --cc=agraf@suse.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).