From: Jonathan Larmour <jlarmour@redhat.com>
To: Tony Ko <nhko@gctsemi.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] MPC860 PC
Date: Thu, 19 Jul 2001 11:46:00 -0000 [thread overview]
Message-ID: <3B572AEF.D66F12D5@redhat.com> (raw)
In-Reply-To: <9860C773D04D834D83FD6FAD00A61E930F2031@gctsemi.gctsemi.com>
Tony Ko wrote:
>
> hi.
> I'm wondering that which register is used for PC (program counter) on
> MPC860.
Sounds like you need a powerPC programming manual, rather than asking on
the eCos list. How about
http://www.mactech.com/articles/mactech/Vol.10/10.08/PowerPcArchitecture/
or just google search on "powerpc architecture manual".
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/
next prev parent reply other threads:[~2001-07-19 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 4:49 Tony Ko
2001-07-19 11:46 ` Jonathan Larmour [this message]
2001-07-20 0:26 Nielsen Linus
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=3B572AEF.D66F12D5@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=nhko@gctsemi.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).