From: Scott Wood <scottwood@freescale.com>
To: Hongtao Jia <hongtao.jia@freescale.com>
Cc: B07421@freescale.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [V2,2/2] powerpc/85xx: workaround for chips with MSI hardware errata
Date: Thu, 27 Jun 2013 21:28:33 -0500 [thread overview]
Message-ID: <20130628022833.GA28050@home.buserror.net> (raw)
In-Reply-To: <1364954598-31914-2-git-send-email-hongtao.jia@freescale.com>
On Wed, Apr 03, 2013 at 10:03:18AM +0800, Hongtao Jia wrote:
> The MPIC version 2.0 has a MSI errata (errata PIC1 of mpc8544), It causes
> that neither MSI nor MSI-X can work fine. This is a workaround to allow
> MSI-X to function properly.
>
> Signed-off-by: Liu Shuo <soniccat.liu@gmail.com>
> Signed-off-by: Li Yang <leoli@freescale.com>
> Signed-off-by: Jia Hongtao <hongtao.jia@freescale.com>
Building on 83xx:
arch/powerpc/sysdev/built-in.o: In function `fsl_of_msi_probe':
fsl_msi.c:(.text+0x1464): undefined reference to `fsl_mpic_primary_get_version'
make[1]: *** [vmlinux] Error 1
make: *** [sub-make] Error 2
fsl_msi.c supports IPIC as well.
-Scott
next prev parent reply other threads:[~2013-06-28 2:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 2:03 [PATCH V3 1/2] powerpc/MPIC: Add get_version API both for internal and external use Jia Hongtao
2013-04-03 2:03 ` [PATCH V2 2/2] powerpc/85xx: workaround for chips with MSI hardware errata Jia Hongtao
2013-06-28 2:28 ` Scott Wood [this message]
2013-07-01 9:36 ` [V2,2/2] " Jia Hongtao-B38951
2013-09-05 4:00 ` Jia Hongtao-B38951
2013-09-05 17:57 ` Scott Wood
2013-09-06 3:19 ` Jia Hongtao-B38951
2013-09-05 18:34 ` [PATCH V2 2/2] " Kumar Gala
2013-09-05 18:37 ` Scott Wood
2013-09-06 15:01 ` Kumar Gala
2013-09-06 15:36 ` Scott Wood
2013-09-06 16:11 ` Kumar Gala
2013-04-03 16:17 ` [PATCH V3 1/2] powerpc/MPIC: Add get_version API both for internal and external use Scott Wood
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=20130628022833.GA28050@home.buserror.net \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=hongtao.jia@freescale.com \
--cc=linuxppc-dev@lists.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).