From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH 0/3] Support for Wind River SBC8641D board
Date: Thu, 10 Apr 2008 19:22:16 -0400 [thread overview]
Message-ID: <1207869739-19892-1-git-send-email-paul.gortmaker@windriver.com> (raw)
The following patches add support for the Wind River SBC8641D board.
I've done it by starting with the current mpc8641_hpcn support and
then making the changes from there, so it should be 1:1 comparable
with the HPCN platform, which aids in tracking/applying future changes.
The SBC8641D support essentially boils down to trimming back stuff
from the HPCN platform, as this board doesn't have the Uli and all
the devices/busses etc. that the HPCN cascades from that. Plus of
course, the dts changes for the localbus specifics.
Patches that aren't included here, but submitted separately are the
support for the Broadcom 5464 quad PHY and the ability to have the
Gianfar TBIPA be auto assigned (since this board puts a PHY at 0x1f).
I expect the defconfig will probably be in an 86xx subdir, based on
what Kumar sent today, but for now it is still in configs. I'm hoping
to see this queued up for 26, if all goes well.
Thanks,
Paul.
next reply other threads:[~2008-04-10 23:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 23:22 Paul Gortmaker [this message]
2008-04-10 23:22 ` [PATCH 1/3] powerpc: Add support for Wind River SBC8641D board Paul Gortmaker
2008-04-10 23:22 ` [PATCH 2/3] powerpc: Add device tree source for Wind River SBC8641D Paul Gortmaker
2008-04-10 23:22 ` [PATCH 3/3] powerpc: Add defconfig for Wind River SBC8641D board Paul Gortmaker
2008-04-11 0:05 ` [PATCH 1/3] powerpc: Add support " Stephen Rothwell
2008-04-11 0:38 ` Michael Ellerman
2008-04-11 1:37 ` Dale Farnsworth
-- strict thread matches above, loose matches on Subject: below --
2008-04-15 22:41 [PATCH 0/3] Support " 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=1207869739-19892-1-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).