Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [WIP] Bare-metal register browsing
Date: Fri, 24 Apr 2015 09:47:00 -0000	[thread overview]
Message-ID: <864mo5yi1x.fsf@gmail.com> (raw)
In-Reply-To: <55349CDB.8010100@codesourcery.com> (Vladimir Prus's message of	"Mon, 20 Apr 2015 09:29:47 +0300")

Vladimir Prus <vladimir@codesourcery.com> writes:

Hi Vladimir,

> The attached patches implement accessing peripheral registers on
> bare-metal targets. Typically,
> these registers are memory-mapped, so one can poke at them using
> memory operations, but it's
> far from convenient. Also, on some targets the registers might require
> a custom way of access,
> which makes things even less convenient.
>
> This patch allows target XML to describe 'spaces' - contains of
> registers, which can be further grouped.
> Given that descrpiption, GDB allows one to do something like:
>
> 	(gdb) print $io.GPIO_PORTF.GPIO_PORTFDIR
> 	$7 = -1
>
> to access registers. One can also do
>
> 	(gdb) ptype $io
>
> to see top-level register groups in space 'io', and so find the
> desired register.

What does the xml using 'spaces' look like?  A small example would be
useful.  Target description "reg" has already had a component "type",
can't we extend "type" for memory-mapped registers?  I am trying to
understand how useful it is to add 'spaces' here.

-- 
Yao (齐尧)


  reply	other threads:[~2015-04-24  9:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20  6:30 Vladimir Prus
2015-04-24  9:47 ` Yao Qi [this message]
2015-04-27 18:25   ` Vladimir Prus
2015-04-27 18:39     ` Vladimir Prus
2015-06-01 18:36     ` Vladimir Prus
2015-06-02 13:00     ` Yao Qi
2015-06-03 19:49       ` Vladimir Prus
2015-06-04 14:38         ` Yao Qi
2015-06-09 20:50           ` Vladimir Prus
2015-06-11  8:56             ` Yao Qi
2015-06-15 13:51               ` Vladimir Prus

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=864mo5yi1x.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vladimir@codesourcery.com \
    /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