From: Matthew Wilcox <matthew@wil.cx>
To: Andrew Park <apark@cdf.toronto.edu>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] architecture overview books?
Date: Fri, 18 Aug 2000 10:24:46 -0400 [thread overview]
Message-ID: <20000818102446.A28421@vodka.thepuffingroup.com> (raw)
In-Reply-To: <Pine.SOL.4.21.0008172141540.26790-100000@misty.cdf>; from Andrew Park on Thu, Aug 17, 2000 at 09:56:01PM -0400
On Thu, Aug 17, 2000 at 09:56:01PM -0400, Andrew Park wrote:
> Hi,
>
> Can all the register information be found in
>
> PCXL_ers.pdf
>
> file? I found it in
>
> http://thepuffingroup.com/parisc/documentation.html
>
> Or are there other sources where I can get architecture overview?
If you check the links at the bottom, there's one to the PA1.1 and PA2.0
Architecture manuals.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2000-08-18 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-15 19:31 [parisc-linux] Question about compatibility T. Martin
2000-08-15 18:43 ` Matthew Wilcox
2000-08-16 14:18 ` David Huggins-Daines
2000-08-18 1:56 ` [parisc-linux] architecture overview books? Andrew Park
2000-08-18 14:24 ` Matthew Wilcox [this message]
2000-08-19 6:51 ` [parisc-linux] gcc make failures Andrew Park
2000-08-30 4:12 ` Matt Taggart
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=20000818102446.A28421@vodka.thepuffingroup.com \
--to=matthew@wil.cx \
--cc=apark@cdf.toronto.edu \
--cc=parisc-linux@thepuffingroup.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