[Xenomai-core] Re: Comedi4xenomai (Was: Re: [Orocos-Dev] [Bug 115] [Project] Move device drivers to orocos-components)

[Xenomai-core] Re: Comedi4xenomai (Was: Re: [Orocos-Dev] [Bug 115] [Project] Move device drivers to orocos-components)

[Alexis Berlemont]

Hi,

> > > This could change fast with e.g. comedi4xenomai in the pipeline...
> >
> > Do you have more information about this?
>
> [putting Alexis Berlemont in cc:, as he is probably the one who can
> answer this question]
> I haven't seen anything on the xenomai MLs lately.  AFAIS from
> <http://svn.gna.org/viewcvs/xenomai/branches/> there hasn't been a lot
> of activity on the branch lately.
>

Sorry for answering so late, I was on holiday.

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.

This is one of the two reasons why you did not notice any change on the comedi 
branch in the SVN trunk the last two months.

The other reason is private, bought a little flat =>  moved out => moved in => 
working on the appartment => all this stuff took and is still taking a lot of 
my spare time ;)

Eventually, if anyone is interested in the new comedi4xeno architecture, I 
will try to commit a reduced version in two or three weeks. 

> I don't know if that means the comedi-over-rtdm code is already in a
> "usable" state as is?

The code available in the trunk is a proof of concept, it does not contain 
real drivers, you can just find test drivers.

Regards.

Alexis.

[Xenomai-core] Re: Comedi4xenomai (Was: Re: [Orocos-Dev] [Bug 115] [Project] Move device drivers to orocos-components)

[Herman Bruyninckx]

On Wed, 2 Aug 2006, Alexis Berlemont wrote:

>>>> This could change fast with e.g. comedi4xenomai in the pipeline...
>>>
>>> Do you have more information about this?
>>
>> [putting Alexis Berlemont in cc:, as he is probably the one who can
>> answer this question]
>> I haven't seen anything on the xenomai MLs lately.  AFAIS from
>> <http://svn.gna.org/viewcvs/xenomai/branches/> there hasn't been a lot
>> of activity on the branch lately.
>>
>
> Sorry for answering so late, I was on holiday.
>
> 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?

Thanks for all your efforts!

Herman

--
   K.U.Leuven, Mechanical Eng.,  Mechatronics & Robotics Research Group
     <http://people.mech.kuleuven.be/~bruyninc> Tel: +32 16 322480

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

Re: [Xenomai-core] Re: Comedi4xenomai

[Jan Kiszka]

[-- 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 --]