From: Jan Kiszka <jan.kiszka@domain.hid>
To: ROSSIER Daniel <Daniel.Rossier@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] RE : Activation of IRQ handler in the Linux domain
Date: Mon, 03 Sep 2007 23:37:19 +0200 [thread overview]
Message-ID: <46DC7E8F.4000503@domain.hid> (raw)
In-Reply-To: <FDBBB5CC70676540B3EF7CFE83FD94E0B475ED@EINT11.einet.ad.eivd.ch>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
Hi Daniel,
[Some add-ons to what Philippe already pointed out:]
ROSSIER Daniel wrote:
> ...
> Ok, I totally agree. I've tried to use a rtdm_event object which I've
> declared in the Linux driver side. Then, the write function is called from a RT task,
That sounds error-prone: Is "write" only called from RT context? Does it
have to synchronise with functions running in non-RT context, and is
this synchronisation done in a RT-safe manner (rtdm_lock_...)? You may
check this offline - or online with CONFIG_IPIPE_DEBUG_CONTEXT.
> then it calls rtdm_event_wait() at a certain point, and the i2c ISR performs a rtdm_event_signal()
> to wake up the RT task. However, I got a kernel crash when rtdm_event_wait() is called.
Sometimes it is helpful to analyse what the crash says precisely, e.g.
at which line of code (during which memory access) the crash happens.
Also, debugging options may help to catch some potential root bug earlier.
In general, I also smell a bit too much hacking and too less designing
here... ;)
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-09-03 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 12:11 [Xenomai-core] Activation of IRQ handler in the Linux domain ROSSIER Daniel
2007-09-03 13:05 ` Philippe Gerum
2007-09-03 17:58 ` [Xenomai-core] RE : " ROSSIER Daniel
2007-09-03 20:31 ` Philippe Gerum
2007-09-03 21:37 ` Jan Kiszka [this message]
2007-09-04 9:23 ` ROSSIER Daniel
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=46DC7E8F.4000503@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Daniel.Rossier@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.