public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Chris Johns <chris@contemporary.net.au>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: selecting a processor variant with gdbarch.
Date: Tue, 01 Nov 2005 09:10:00 -0000	[thread overview]
Message-ID: <436730E3.9040700@contemporary.net.au> (raw)
In-Reply-To: <20051031141943.GC25504@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Mon, Oct 31, 2005 at 07:08:53PM +1100, Chris Johns wrote:
> 
>>Hello,
>>
>>What is the preferred way to have gdbarch select a specific processor 
>>variant ?
> 
> 
> Can you be more specific about what you want?
> 

On the Coldfire we have a growing number of processors with a few 
different cores each running the same code, yet with register sets that 
vary in different ways.

When using BDM with a Coldfire you need to get at some of the processor 
specific registers to access memory controllers to enable RAM to 
download a program.

We can teach a BDM target ops how to detect various processors and make 
the selection. Getting gdbarch to handle the change is what I would like 
to understand.

> 
>>How can a target op inform the gdbarch what the specific processor is ?
> 
> 
> Not yet, but I'm working on implementing that.
> 

I have played around with changing the register names and types but 
regcache proved a hurdle. It sets up the cache once during 
initialisation. If I could make a a call to get regcache to 
re-initialise this hurdle could be overcome.


Chris

  reply	other threads:[~2005-11-01  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31  8:09 Chris Johns
2005-10-31 14:19 ` Daniel Jacobowitz
2005-11-01  9:10   ` Chris Johns [this message]
2005-11-07  0:22     ` Daniel Jacobowitz
2005-11-07  0:37     ` Daniel Jacobowitz

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=436730E3.9040700@contemporary.net.au \
    --to=chris@contemporary.net.au \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).