From: Eugene Surovegin <ebs@ebshome.net>
To: Shawn Jin <shawnxjin@gmail.com>
Cc: Linuxppc-embedded@ozlabs.org
Subject: Re: PPC440GP and Ebony board, ask for documents
Date: Thu, 3 Feb 2005 16:28:53 -0800 [thread overview]
Message-ID: <20050204002853.GA1714@gate.ebshome.net> (raw)
In-Reply-To: <c3d0340b05020315567d2ce3e4@mail.gmail.com>
On Thu, Feb 03, 2005 at 03:56:51PM -0800, Shawn Jin wrote:
> I have an IBM eBony board without any documents. Since IBM pulled off
> all the documents related ppc440 after they sold the business to AMCC,
> googling cannot find any documents about eBony schematics, board's
> user manual and evaluation board kit user's manual.
All these documents are available at AMCC web.
--
Eugene
next prev parent reply other threads:[~2005-02-04 0:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 23:56 PPC440GP and Ebony board, ask for documents Shawn Jin
2005-02-04 0:28 ` Eugene Surovegin [this message]
2005-02-04 0:43 ` Shawn Jin
2005-02-04 1:01 ` Eugene Surovegin
2005-02-04 1:12 ` Shawn Jin
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=20050204002853.GA1714@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=Linuxppc-embedded@ozlabs.org \
--cc=shawnxjin@gmail.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 NNTP newsgroup(s).