From: Wolfgang Grandegger <wg@domain.hid>
To: Klaas Gadeyne <klaas.gadeyne@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Shared IRQ issue with Xeno Peak PCI CAN driver
Date: Wed, 05 Mar 2008 14:05:22 +0100 [thread overview]
Message-ID: <47CE9A92.10206@domain.hid> (raw)
In-Reply-To: <Pine.LNX.4.64.0803051337420.394@domain.hid>
Klaas Gadeyne wrote:
> On Wed, 5 Mar 2008, Wolfgang Grandegger wrote:
>> Klaas Gadeyne wrote:
>>> Hi,
>>>
>>> we're having a problem finding a non-shared IRQ for a PEAK systems can
>>> board in a particular industrial SBC with PCI backplane [*].
>>> Loading the xeno_can_peak_pci driver fails due to a "so-called" IRQ
>>> conflict. (see below)
>>>
>>> However, it seems the IRQ (12) is not assigned, so this shouldn't be a
>>> problem [**]?
>
> [...]
>>> Any hints on how to debug this? We've already tried everything
>>> described in the FAQ (I guess), but we don't understand there's a
>>> conflict even if nothing is listed in /proc/interrupts?
>>
>> There are two CAN controllers on the card, right? Therefore you need
>> support for shared interrupts. Actually, requesting the IRQ 12 for the
>> second CAN controller fails because it's already used by the first one.
>
> Thx! (we've just found out ourselves that the difference in behaviour
> between the 2 pc's was indeed due to different xenomai versions
> (<http://svn.gna.org/viewcvs/xenomai?rev=3291&view=rev>).
Well, yes. Since commit 3291
http://svn.gna.org/viewcvs/xenomai?rev=3291&view=rev
the driver does not tolerate that failure any more. Do you prefer the
old behavior (ignoring the failure and using just the first channel)?
Wolfgang.
next prev parent reply other threads:[~2008-03-05 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 17:12 [Xenomai-help] Shared IRQ issue with Xeno Peak PCI CAN driver Klaas Gadeyne
2008-03-05 11:34 ` Wolfgang Grandegger
2008-03-05 12:41 ` Klaas Gadeyne
2008-03-05 13:05 ` Wolfgang Grandegger [this message]
2008-03-05 13:40 ` Klaas Gadeyne
2008-03-05 13:54 ` Jan Kiszka
2008-03-06 11:35 ` Wolfgang Grandegger
2008-03-07 12:54 ` Jan Kiszka
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=47CE9A92.10206@domain.hid \
--to=wg@domain.hid \
--cc=klaas.gadeyne@domain.hid \
--cc=xenomai@xenomai.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 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.