From: "dong in kang" <dkang@east.isi.edu>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Need opinions: Porting PPC linux for a custom Prep board.
Date: Fri, 11 Jul 2003 11:50:49 -0400 [thread overview]
Message-ID: <000901c347c4$33488a60$45a97241@Minjoo> (raw)
In-Reply-To: <20030711153310.7DD2FC6D82@atlas.denx.de>
Hello,
I'm trying to port MontaVista Linux for a custom Prep board.
The CPU is a variant of IBM PPC750, and the PCI bridge chip is a variant of
MPC106.
The architecture of the CPU is same as IBM PPC750.
The architecture of the bdidge chip is a superset of MPC106.
Any suggestion which code should I start with?
I found some prep specific routines under arch/ppc/platform directory.
The codes seem to work for two targets, IBM prep and Motorolla prep.
If I had better start with one of them, which would be better?
Thank you,
Dong-In
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-07-11 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 15:12 AgileDB and Abatron BDI 2000 ICE Steven Rothweiler
2003-07-11 15:33 ` Wolfgang Denk
2003-07-11 15:50 ` dong in kang [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='000901c347c4$33488a60$45a97241@Minjoo' \
--to=dkang@east.isi.edu \
--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).