linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH 0/3] Powerpc support for SBC8548 board
Date: Fri, 21 Dec 2007 01:43:50 -0500	[thread overview]
Message-ID: <11982194332672-git-send-email-paul.gortmaker@windriver.com> (raw)


The following three patches add support for the Wind River SBC8548 board
onto the powerpc branch.  The patches are as follows:

1) Add basic support for Wind River SBC8548 as powerpc

This adds in the basic platform support file -- closely matching that which
exists for the MPC8548CDS board.  These are layered on top of the earlier
SBC8560 patches (only is an issue for the usual Makefile/Kconfig patch
collisions).

 powerpc/arch/powerpc/platforms/85xx/Kconfig   |   10 +
 powerpc/arch/powerpc/platforms/85xx/Makefile  |    1 
 powerpc/arch/powerpc/platforms/85xx/sbc8548.c |  182 ++++++++++++++++++++++++++
 3 files changed, 191 insertions(+), 2 deletions(-)


2) Add device tree source for Wind River SBC8548 board

This also closely matches what exists for the MPC8548CDS platform.  The big
difference here is that this board doesn't have physical access to PCI#2
and it doesn't have the CDS's bridges, i8259, peripherals, etc, so the dts
is overall quite a bit smaller.  I've believe I've got all aliases and the
associated gianfar updates etc. that I'd somehow missed in the sbc8560 dts.

 powerpc/arch/powerpc/boot/dts/sbc8548.dts |  219 ++++++++++++++++++++++++++++++
 1 file changed, 219 insertions(+)


3) Add default .config file for Wind River SBC8548

This config gives basic serial console and ethernet support for doing an
NFS root setup.  The SBC8548 has one PCI-X slot, and a short PCI-e slot,
so I've enabled PCI.  

 powerpc/arch/powerpc/configs/sbc8548_defconfig |  740 +++++++++++++++++++++++++
 1 file changed, 740 insertions(+)


Like the 8560 board, I'd quickly spun together a u-boot 1.2.0 for testing
this -- since that was the quickest route for me to get a powerpc capable
version.  This too needs a proper u-boot 1.3.1 patchset so we get all the
associated updates within that, like local-mac-address etc.  Soon...

Paul.

             reply	other threads:[~2007-12-21  6:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21  6:43 Paul Gortmaker [this message]
     [not found] ` <567bfb934387ec732a4c52c26efd17856f5144fd.1198217984.git.paul.gortmaker@windriver.com>
2007-12-21  6:43   ` [PATCH 1/3] sbc8548: Add basic support for Wind River SBC8548 as powerpc Paul Gortmaker
2007-12-21 15:32     ` Kumar Gala
2008-01-07 22:27       ` Paul Gortmaker
2008-01-07 22:40       ` [PATCH] sbc85xx: remove PCI exclude device for sbc8548/sbc8560 Paul Gortmaker
2008-01-08  6:15         ` Kumar Gala
     [not found]   ` <a9ccacef3dee433c1bc90cd73ef84ba26a2870bb.1198217984.git.paul.gortmaker@windriver.com>
2007-12-21  6:43     ` [PATCH 2/3] sbc8548: Add device tree source for Wind River SBC8548 board Paul Gortmaker
2007-12-21 15:33       ` Kumar Gala
2007-12-21 17:20         ` Paul Gortmaker
2007-12-22  2:05           ` David Gibson
     [not found]   ` <e954b4255110df8c9ac5c636af4ea4394ea1e953.1198217984.git.paul.gortmaker@windriver.com>
2007-12-21  6:43     ` [PATCH 3/3] sbc8548: Add default .config file for Wind River SBC8548 Paul Gortmaker

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=11982194332672-git-send-email-paul.gortmaker@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=linuxppc-dev@ozlabs.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).