From: Philippe Gerum <rpm@xenomai.org>
To: Srikanth C <srikanthc9@gmail.com>
Cc: Xenomai@xenomai.org
Subject: Re: [Xenomai] Spurious interrupt are raised with 2.6.1 xenomai patch
Date: Fri, 26 Apr 2013 16:46:23 +0200 [thread overview]
Message-ID: <517A933F.6020908@xenomai.org> (raw)
In-Reply-To: <5178F226.7090206@xenomai.org>
On 04/25/2013 11:06 AM, Philippe Gerum wrote:
> On 04/25/2013 11:03 AM, Philippe Gerum wrote:
>> On 04/25/2013 09:57 AM, Srikanth C wrote:
>>> Test Results with adeos-ipipe patch:
>>>
>>> H/W Setup is same, S/W Changed to adeos-ipipe with 3.0.8 kernel.
>>>
>>> adeos-ipipe-3.0.8-powerpc-2.13-04.patch applied to 3.0.8 kernel,
>>> spurious interrupt is not raised with this patch.
>>>
>>
>> I still don't know what ppc platform you are running on, which does not
>> allow me to figure out which interrupt controller might be involved, and
>> how to try reproducing this issue.
>>
>> Again and I won't ask for this once more:
>>
>> - what is your ppc platform: 40x, 44x, 52xx, 82xx, 83xx, 85xx, 86xx,
>> anything else?
>
> I need the cpu type _and_ the board type. Attaching your kernel .config
> would provide the required information.
CONFIG_PCI_MSI as found in your configuration won't work, with any past
or current pipeline release for powerpc (3.0.8 was certainly a fluke, or
MSI was disabled there). The IRQ chip handlers are still attempting to
mask the MSI source upon interrupt, which won't fly in the I-pipe case.
--
Philippe.
next prev parent reply other threads:[~2013-04-26 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 6:29 [Xenomai] Spurious interrupt are raised with 2.6.1 xenomai patch Srikanth C
2013-04-24 6:49 ` Gilles Chanteperdrix
2013-04-24 6:57 ` Srikanth C
2013-04-24 8:59 ` Philippe Gerum
2013-04-24 9:33 ` Srikanth C
2013-04-25 7:57 ` Srikanth C
2013-04-25 9:03 ` Philippe Gerum
2013-04-25 9:06 ` Philippe Gerum
2013-04-26 14:46 ` Philippe Gerum [this message]
2013-04-26 18:49 ` Srikanth C
2013-04-29 19:27 ` Srikanth C
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=517A933F.6020908@xenomai.org \
--to=rpm@xenomai.org \
--cc=Xenomai@xenomai.org \
--cc=srikanthc9@gmail.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 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.