From: fche@redhat.com (Frank Ch. Eigler)
To: "Tom Taylor" <ttaylor@ateng.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: PSIM Support for MPC860
Date: Mon, 08 Oct 2001 12:34:00 -0000 [thread overview]
Message-ID: <o5adz22afy.fsf@touchme.toronto.redhat.com> (raw)
In-Reply-To: <014301c1501f$a3a3bdf0$7c01a8c0@ateng.com>
"Tom Taylor" <ttaylor@ateng.com> writes:
: I'm attempting to use the GDB 5.0 PSIM simulator to analyze firmware
: written for the MPC860T in the OEA mode. [...]
You might have a big job ahead of you.
: I have noticed that there is special code for handling problematic
: MPC860 forward branches [...] Is this because only application code
: was being simulated [...]
Yes.
: If I undertake the task of adding MPC860 support to PSIM, is there any
: interest in the GDB community for simulating this processor,
Sure.
: and is there any available code that could be used to reduce the
: time and effort this task will require?
I don't know of any. Building satisfactory simulations of complex
processors tends to be a big job. (Red Hat does this sort of thing on
contract basis for example.)
- FChE
next prev parent reply other threads:[~2001-10-08 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 10:35 Tom Taylor
2001-10-08 12:34 ` Frank Ch. Eigler [this message]
2001-10-08 13:53 ` Tom Taylor
2001-10-08 16:42 ` Frank Ch. Eigler
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=o5adz22afy.fsf@touchme.toronto.redhat.com \
--to=fche@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=ttaylor@ateng.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