From: Jan Kiszka <jan.kiszka@domain.hid>
To: Alexis Berlemont <berlemont.hauw@domain.hid>
Cc: Orocos Developers <orocos-dev@domain.hid>,
xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Re: Comedi4xenomai
Date: Wed, 02 Aug 2006 08:18:14 +0200 [thread overview]
Message-ID: <44D043A6.3070902@domain.hid> (raw)
In-Reply-To: <Pine.LNX.4.64.0608020735160.5922@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Herman Bruyninckx wrote:
> On Wed, 2 Aug 2006, Alexis Berlemont wrote:
>>
>> comedi-over-rtdm is currently undergoing deep modifications. I am
>> trying to
>> redefine an architecture more suitable for RTDM. That implies I am
>> rewriting
>> a big chunk of the Comedi code and its drivers without commiting into
>> SVN.
>>
>> I thought it was a bad idea to commit broken code (It does not even
>> compile).
>> Tell me if I'm wrong.
>
> You are right! But maybe it could be good to discuss your architecture on
> the xenomai mailinglist?
Ack. I would be interested in learning more details about the
differences between original comedi (which I still don't know well
enough) and your design. Will the user notice it? What will change for
comedi driver developers? How will the RTDM profile of comedi look like?
And I think that it could be helpful for such a discussion to update the
code in your branch - even if its not compiling.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
prev parent reply other threads:[~2006-08-02 6:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 22:50 [Xenomai-core] Re: Comedi4xenomai (Was: Re: [Orocos-Dev] [Bug 115] [Project] Move device drivers to orocos-components) Alexis Berlemont
2006-08-02 5:36 ` Herman Bruyninckx
2006-08-02 6:18 ` Jan Kiszka [this message]
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=44D043A6.3070902@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=berlemont.hauw@domain.hid \
--cc=orocos-dev@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.