From: Philippe Gerum <rpm@xenomai.org>
To: Hannes Mayer <h.mayer@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] rt_intr_create returns ENOSYS ?
Date: Wed, 26 Jul 2006 11:25:30 +0200 [thread overview]
Message-ID: <1153905930.4946.63.camel@domain.hid> (raw)
In-Reply-To: <44C532B8.3070100@domain.hid>
On Mon, 2006-07-24 at 22:51 +0200, Hannes Mayer wrote:
> Ciao Philippe!
>
> Philippe Gerum wrote:
> [...]
> >>>> Any enlightenment very much appreciated!
> >>> CONFIG_XENO_OPT_NATIVE_INTR? It's default off now.
> >> Yeah, works. Thanks! :-)
> >>
> >> What's the reason for defaulting to off ?
> >> Force users to write RTDM stuff ?
> >
> > This gives a strong hint about what would be a good design decision when
> > crafting a device driver over Xenomai: i.e. use RTDM.
>
> Absolutely, but if one just wants to capture the parallel
> port int, I think it's a little overkill to make a driver
> for it.
>
> Anyway, is that documented somewhere, that
> CONFIG_XENO_OPT_NATIVE_INTR is default off now and that
> folks should preferably make RTDM drivers now ?
> I'd suggest to add that somewhere...
>
It's already present in OPT_NATIVE_INTR's help section for 2.6, but this
is missing for 2.4 (no Xenomai help strings available with 2.4
actually).
> Tanti saluti,
> Hannes.
>
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
--
Philippe.
next prev parent reply other threads:[~2006-07-26 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 20:51 [Xenomai-help] rt_intr_create returns ENOSYS ? Hannes Mayer
2006-07-26 9:25 ` Philippe Gerum [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-23 19:34 Hannes Mayer
2006-07-23 20:01 ` Jan Kiszka
2006-07-23 20:48 ` Hannes Mayer
2006-07-23 20:55 ` Jan Kiszka
2006-07-23 21:25 ` Philippe Gerum
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=1153905930.4946.63.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=h.mayer@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.