From: Michael Ellerman <michael@ellerman.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Olof Johansson <olof@lixom.net>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Phillips Kim <Kim.Phillips@freescale.com>,
Jin Zhengxiong <Jason.Jin@freescale.com>,
Li Tony <Tony.Li@freescale.com>
Subject: Re: [PATCH 2/2] powerpc: Add IPIC MSI support
Date: Fri, 14 Dec 2007 20:40:23 +1100 [thread overview]
Message-ID: <1197625223.18300.1.camel@concordia> (raw)
In-Reply-To: <90B908AC-E879-4046-AAFC-FE79EB78A932@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Fri, 2007-12-14 at 02:52 -0600, Kumar Gala wrote:
> On Dec 14, 2007, at 2:47 AM, Li Tony wrote:
>
> >
> > Hi,
> >
> > I think it is possible to make common code to support both IPIC and
> > MPIC.
> > Currently, the MPIC has already implemented MSI which is different
> > from IPIC and embedded into the mpic code body.
> > If want to unifiy MSI code, we need to remove the current MPIC MSI
> > implementation.
>
> The MPIC is going to have to support several MSI styles (IBM/U3,
> PaSemi, and FSL) since we all seem to handle it differently.
I haven't really looked at the similarities or differences, but I think
Kumar is right, MPIC is going to have to (and already does) support
different styles.
If there's some commonality that can be shared I'm all ears, patches
welcome ;)
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-12-14 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 10:39 [PATCH 2/2] powerpc: Add IPIC MSI support Li Li
2007-12-04 10:57 ` Li Yang
2007-12-04 11:59 ` Michael Ellerman
2007-12-14 5:44 ` Kumar Gala
2007-12-14 8:47 ` Li Tony
2007-12-14 8:52 ` Kumar Gala
2007-12-14 9:13 ` Li Li
2007-12-14 9:39 ` Jin Zhengxiong
2007-12-14 9:40 ` Michael Ellerman [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=1197625223.18300.1.camel@concordia \
--to=michael@ellerman.id.au \
--cc=Jason.Jin@freescale.com \
--cc=Kim.Phillips@freescale.com \
--cc=Tony.Li@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.