From: Ignaz Forster <ignaz.forster@gmx.de>
To: gdb@sourceware.org
Subject: Support for PPC405 / PPC440 registers
Date: Mon, 26 Mar 2007 20:26:00 -0000 [thread overview]
Message-ID: <46082CD9.6080002@gmx.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I recently tried to debug an embedded IBM PowerPC 405 and 440 over JTAG.
The necessary GDB stub was written by myself (unfortunately using
confidential information, so I won't be able to publish it).
When trying to display the contents of the processor's registers I
noticed only the PPC403 register layout was included in the standard GDB
distribution. As the registers of the different processors in the
4xx-series differ, I tried to modify GDB and BFD to handle the registers
of the additional processors. The following files were changed:
- - bfd/cpu-powerpc: Added definitions for the additional processors in
the struct 'bfd_powerpc_archs'
- - bfd/archures.c: Added processors in 'bfd_architecture'
- - gdb/ppc-tdep.h: Added SPR numbers for new registers
- - gdb/rs6000-tdep.c: Added processors to the struct 'variants' and
created appropriate 'static const struct reg registers_...' entries with
the available registers
After that the registers showed up and could be used after setting the
new processors with "set architecture".
Question 1: What did I destroy by doing this?
Question 2: Would a patch to add support for these processors be useful?
What else should be done before even thinking about doing so?
Thanks,
- --
Ignaz Forster <ignaz.forster@gmx.de>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFGCCzZ/2+SjQTlQJkRArxWAJ4qrRKwQkaD/0qIuPMaYrAT4TxjSwCgkt7i
W99pT7iGjJ49m3BUO76LeRk=
=xvW9
-----END PGP SIGNATURE-----
next reply other threads:[~2007-03-26 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 20:26 Ignaz Forster [this message]
2007-03-26 20:38 ` Daniel Jacobowitz
2007-03-27 20:33 ` Ignaz Forster
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=46082CD9.6080002@gmx.de \
--to=ignaz.forster@gmx.de \
--cc=gdb@sourceware.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