From: Jan Kiszka <kiszka@domain.hid>
To: Herman Bruyninckx <herman.bruyninckx@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Future of fusion
Date: Thu, 13 Oct 2005 11:46:56 +0200 [thread overview]
Message-ID: <434E2D10.7070208@domain.hid> (raw)
In-Reply-To: <Pine.LNX.4.64.0510131033300.5110@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
Herman Bruyninckx wrote:
> On Thu, 13 Oct 2005, Philippe Gerum wrote:
> [...]
>
>> - Drivers: Now that we have a deeply integrated port of RTDM, what's
>> next? Field busses and other industrial gizmos anyone?
>
>
> That's an interesting avenue for all our machine control oriented realtime
> applications. But this avenue is full of incomplete or non-free
> specifications and interfaces...
>
Indeed, but we cannot solve all problems at once. Let's start with those
devices which are more or less open (and there are already a lot). Let's
also try to propagate the message that RTDM is the prefered way to
provide real-time drivers. And if someone comes up with a new driver,
check if its interface is generic enough to implement it for similar
devices as well (=>generic device profiles).
Far from being perfect, but there are first efforts for such profiles:
Serial (as it comes with Xenomai), process image (see the Hilscher
Interbus driver I once announced), or CAN (yet a bit in flux, but things
slowly stabilises here). Plans exist to go the same way for low level
access to FireWire or USB. And you can even map whole protocol stacks
onto RTDM, like UDP/IP (RTnet) or also CANopen. The enables thrilling
combinations without the need to rewrite your application.
The interest in such progress is there, not yet on the vendor side, but
on the user side - including many industrial users. And they can push
things forward as well, finally making at least some vendors more
cooperative, too.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2005-10-13 9:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 7:55 [Xenomai-core] Future of fusion Marco Cavallini
2005-10-13 8:15 ` Jan Kiszka
2005-10-13 8:24 ` Philippe Gerum
2005-10-13 8:37 ` Herman Bruyninckx
2005-10-13 8:50 ` Gilles Chanteperdrix
2005-10-13 8:54 ` Herman Bruyninckx
2005-10-13 9:12 ` Philippe Gerum
2005-10-13 9:34 ` Herman Bruyninckx
2005-10-13 13:57 ` Jan Kiszka
2005-10-13 19:57 ` Gilles Chanteperdrix
2005-10-13 9:46 ` Jan Kiszka [this message]
2005-10-13 10:46 ` Paul
2005-10-13 13:33 ` Philippe Gerum
2005-10-13 19:47 ` Wolfgang Grandegger
2005-10-13 20:28 ` Gilles Chanteperdrix
2005-10-14 3:42 ` Romain Lenglet
2005-10-16 7:47 ` [Xenomai-core] Packaging issues and licensing issues Romain Lenglet
2005-10-16 7:50 ` Gilles Chanteperdrix
2005-10-16 14:00 ` gna-dev
2005-10-16 14:18 ` Romain Lenglet
2005-10-17 18:54 ` 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=434E2D10.7070208@domain.hid \
--to=kiszka@domain.hid \
--cc=herman.bruyninckx@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.