From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Zang Roy-r61911 <tie-fei.zang@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc: Support for "weird" MPICs and fixup mpc7448_hpc2
Date: Sat, 26 Aug 2006 08:50:13 +1000 [thread overview]
Message-ID: <1156546214.8433.331.camel@localhost.localdomain> (raw)
In-Reply-To: <1156492062.7107.26.camel@localhost.localdomain>
On Fri, 2006-08-25 at 15:47 +0800, Zang Roy-r61911 wrote:
> On Fri, 2006-08-25 at 12:16, Benjamin Herrenschmidt wrote:
> > This patch is a slightly cleaned up version of Zang Roy's support for
> > the TSI108 MPIC variant. It also fixes up MPC7448_hpc2 to use the new
> > version of the type macros and changes the way MPIC is selected in
> > Kconfig to better match what is done for other system devices.
> >
> > Signed-off-by: Roy Zang <tie-fei.zang@freescale.com>
> > Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > ---
> >
> > Zang Roy, please verify that it still works for you. I've tested it on
> > an Apple G5 with and without CONFIG_MPIC_WEIRD .
> >
>
> It works OK on my mpc7448hpc2 board.
> There is a sequence for the patch applying.
>
> (1) patch for IRQ update for mpc7448hpc2:
> http://ozlabs.org/pipermail/linuxppc-dev/2006-August/025559.html
>
> (2) the weird mpic patch repost by your mail.
> (3) the following minor patch to build mpic.o for CONFIG_MPIC_WEIRD
The later shouldn't be needed.
CONFIG_MPIC_WEIRD is an _addition_ to CONFIG_MPIC. That is, for example,
your HPC2 platform should define both CONFIG_MPIC and CONFIG_MPIC_WEIRD
Ben.
prev parent reply other threads:[~2006-08-25 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 4:16 [PATCH] powerpc: Support for "weird" MPICs and fixup mpc7448_hpc2 Benjamin Herrenschmidt
2006-08-25 7:47 ` Zang Roy-r61911
2006-08-25 22:50 ` Benjamin Herrenschmidt [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=1156546214.8433.331.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=tie-fei.zang@freescale.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).