linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "dony" <dony.he@huawei.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Which board use 8260 CPU?
Date: Mon, 26 Feb 2001 21:04:59 +0100	[thread overview]
Message-ID: <20010226200504.00F03287EA@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 26 Feb 2001 19:40:08 +0800." <000901c09fe8$def06760$8021690a@huawei.com>


In message <000901c09fe8$def06760$8021690a@huawei.com> you wrote:
>
>     I just downloaded ppcboot.tar.gz files.
>    Since my custom board use 8260, I want to find a board  using 8260 from ppcboot/board as a example.  I know "cogent"  board supports 8260, but it seems to be a little complex for me.
> Are there other boards using  8260 CPU which can meet the following requirements:

Just check the top  level  Makefile;  it  contains  targets  for  all
standard board configurations, and the definition of the CPU variable
give  you  some hints; there are 3 boards with 82xx CPU at the moment
(some more in the works): sandpoint (8240), hymod (8260)  and  cogent
(8260).

>  1  Initialize CPU core registers , SDRAM, MMU,SIU, CPM
>  2  Initialize Serial Port and Network (SMC , FCC).
> 3  Download kernel from tftp server or load kernel from on-board flash ?

AFAIK, all of them do that.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
The software required `Windows 95 or better', so I installed Linux.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2001-02-26 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010222074732.6B566281D9@denx.denx.de>
2001-02-26 11:40 ` Which board use 8260 CPU? dony
2001-02-26 15:10   ` Murray Jensen
2001-02-26 20:04   ` Wolfgang Denk [this message]

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=20010226200504.00F03287EA@denx.denx.de \
    --to=wd@denx.de \
    --cc=dony.he@huawei.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).