From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Ivan Kalatchev <ivan.kalatchev@domain.hid>
Cc: 'Xenomai help' <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Viper board (ARM XScale) problems with Xenomai-2.4.10
Date: Tue, 12 Jan 2010 22:09:33 +0100 [thread overview]
Message-ID: <4B4CE50D.20907@domain.hid> (raw)
In-Reply-To: <003e01ca93cb$45fb6d30$d1f24790$@kalatchev@domain.hid>
Ivan Kalatchev wrote:
>>> May be there should be some sort of Howto about it on Xenomai
>>> site?
>> Actually this is described in the howto porting the I-pipe for arm
>> to a new board: http://www.xenomai.org/index.php/I-
>> pipe:ArmPorting#New_variables_and_functions see ipipe_irq_mux_p and
>> ipipe_demux_irq
>>
>> But the problem is that the generic code changed and I missed that
>> change, so the old way is documented, not the new one.
>
> I actually read that document, but thing is that CPLD interrupt on
> Viper is not MUX interrupt, although it is chained interrupt. That's
> why I missed it. So may be HOWTO should still mention chained
> interrupts specifically in addition to MUX interrupts. Just a
> thought.
Chained interrupt and muxed interrupt are the same thing.
--
Gilles Chanteperdrix, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-01-12 21:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 22:04 [Xenomai-help] Viper board (ARM XScale) problems with Xenomai-2.4.10 Ivan Kalatchev
2010-01-11 23:01 ` Gilles Chanteperdrix
2010-01-12 10:29 ` Gilles Chanteperdrix
[not found] ` <001f01ca9390$5fa20db0$1ee62910$@kalatchev@domain.hid>
2010-01-12 14:18 ` Gilles Chanteperdrix
2010-01-12 15:12 ` Ivan Kalatchev
2010-01-12 15:35 ` Gilles Chanteperdrix
2010-01-12 16:09 ` Ivan Kalatchev
2010-01-12 16:16 ` Gilles Chanteperdrix
2010-01-12 17:39 ` Ivan Kalatchev
2010-01-12 17:43 ` Gilles Chanteperdrix
2010-01-12 20:04 ` Gilles Chanteperdrix
2010-01-12 20:34 ` Ivan Kalatchev
2010-01-12 22:40 ` Ivan Kalatchev
2010-01-12 22:42 ` Gilles Chanteperdrix
2010-01-12 22:48 ` Ivan Kalatchev
2010-01-12 22:52 ` Gilles Chanteperdrix
2010-01-12 23:28 ` Gilles Chanteperdrix
2010-01-13 0:20 ` Gilles Chanteperdrix
2010-01-13 13:55 ` Ivan Kalatchev
2010-01-13 13:59 ` Gilles Chanteperdrix
2010-01-12 21:07 ` Ivan Kalatchev
2010-01-12 21:09 ` Gilles Chanteperdrix [this message]
2010-01-12 21:27 ` Ivan Kalatchev
2010-01-12 21:30 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2010-01-11 18:22 Ivan Kalatchev
2010-01-11 18:28 ` Gilles Chanteperdrix
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=4B4CE50D.20907@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=ivan.kalatchev@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.