From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Another ARM question
Date: Mon, 14 Mar 2005 08:37:50 -0700 [thread overview]
Message-ID: <Pine.LNX.4.58.0503140836030.22631@enigma.lanl.gov> (raw)
In-Reply-To: <ec52b6dd6e03350b5ce5d90ff274873a@coraid.com>
On Sat, 12 Mar 2005, Brantley Coile wrote:
> I'm about to use Plan 9's 5? to write the code for our next storage
> blade, which has a ep9312. What is the best book, manual, etc to get
> me up to speed on the ARM architecture as quickly as possible?
google 9312 and you should get to cirrus.com
are you porting plan 9 as well?
Here are the docs I am using for my work:
DDI0151C_920T_TRM.pdf
EP9301_PP4.pdf
EP9301_User_Guide.pdf
I found the 920T doc on the arm website in the uk.
The other two are cirrus, IIRC.
ron
next prev parent reply other threads:[~2005-03-14 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 14:55 Brantley Coile
2005-03-14 15:37 ` Ronald G. Minnich [this message]
2005-03-14 15:52 ` Brantley Coile
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=Pine.LNX.4.58.0503140836030.22631@enigma.lanl.gov \
--to=rminnich@lanl.gov \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).