From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: linuxppc-embedded@ozlabs.org
Cc: p_gortmaker@yahoo.com
Subject: [PATCH 0/5] Updates for WRS SBC82xx boards
Date: Thu, 25 May 2006 14:15:55 -0400 [thread overview]
Message-ID: <20060525181554.GB679@windriver.com> (raw)
There are five patches required to use the WRS SBC8265 board (with PCI).
The biggest issue was the earlier cleanup/replacement of m8260_pci with
m82xx_pci -- in the process it became specific to the PQ2FADS.
I've booted on 2.6.17rc3, and they still apply to 17rc4-git12 snapshot,
but I wouldn't be surprised if the CPM UART changes in rc3 --> rc4 break
sbc82xx CPM serial as I see Vitaly is still working on that.
Paul.
----
patch1: sbc82xx-diff0
- replace NR_SIU_INTS with NR_CPM_INTS
patch2: sbc82xx-PCI-diff1
- allow m82xx_pci.c to be used by other platforms that have
their own map_irq
patch3: sbc82xx-CONFIG.diff1
- add CONFIG_SBC82xx alongside CONFIG_PQ2FADS where required.
patch4: sbc82xx-mchk-pci9.diff1
- restore machine check disable for PCI9 that was in earlier
m8260_pci.c
patch5: fcc_enet-mac-addr.diff1
- restore proper collection of mac addr data in obsolete FCC
driver by replacing mix of #ifdef and if() with case
reply other threads:[~2006-05-25 22:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060525181554.GB679@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=p_gortmaker@yahoo.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).