Re: RTAI status

Brooke Wallace <[email protected]> Thu, 16 Feb 2017 17:30:31 +0000
Newsgroups gmane.linux.real-time.rtai
Message-ID <3634DB8ABD61FB48A0AC3D017E9C37A855E21321@ORD2MBX09A.mex05.mlsrvr.com>
Thanks for the info. It looks like a good project to work with. I'm relaying this to my team.

Is there an effort to translate the documentation to English? I recall poking around and find a lot of it in Spanish or something.

And what about GIT? you mention Vulcano CVS below. Is there a GIT repository yet?

-Brooke
________________________________________
From: Torsten Koschorrek [[email protected]]
Sent: Tuesday, February 14, 2017 2:21 PM
To: Paolo Mantegazza; Brooke Wallace; [email protected]
Subject: Re: [Rtai] RTAI status

Hi all,

I'm the maintainer for ARM.

Just like Paolo I don't have as much time as I like for RTAI, especially
after switching my employer some time back. Still I'm willing to and do
work for the project.

This means primarily to support people who want to work with ARM in RTAI
and help them to do the porting or setting up of the system. I also have
some minor and bigger work packages and ideas which are only waiting for
being implemented. This would also include an update of the RTAI project
page for example ;-) to let people know that the project is still active
and to reflect the current status.

Torsten



On 14.02.2017 10:38, Paolo Mantegazza wrote:
> RTAI is at the state of version 5.0-test. It has not been released as
> 5.0 final because I've pending issues on RTDM support and I did not find
> yet the time to work on it.
> In any case, RTDM apart, Vulcano CVS is in a good shape and working.
>
> The point is that  I'm intensely using it now, and I've not found much
> time to care for a release. That's bad but, on the good side, I'm still
> seeing RTAI working nicely and effectively, hands on and on significant
> problems.
>
> My coding is straight in C but in my dept there reappeared (lazy) people
> that like getting their controllers generated automatically. Thus I soon
> foresee some refurbishing of RTAI-Lab also.
>
> All of what above, at least in relation of what we are doing, has also
> shown that the interface with COMEDI is still working properly.
>
> There is some ARM support, with an own maintainer, in RTAI, but I'm not
> working on it. Nevertheless I've a plan to acquaint myself with
> Rapsberry. I did something already, e.g saw that I can develop my stuff
> much like as on a PC. Unfortunately the lack of a boot-loader makes
> kernel level (patching) development quite annoying. I've been said there
> might be the possibility of using a boot-loader but did not verify it
> yet. Development using a virtual environment is not my choice.
>
> Overall it is all a matter of time, at the moment there are 3 people
> working on RTAI, 2 just (very) sparingly. After my retirement I hoped to
> have more time to dedicate to RTAI. (Un?)Fortunately my continued
> engagement with my dept research activities proved it was not that way.
>
> In any case I find RTAI as lively as before, at least on my side and for
> not so trivial applications.
>
> It would be helpful to find people willing to supporting some RTAI
> subsystems development, e.g. RTDM, RTAI-Lab and COMEDI updates.
>
> Paolo
>
> On 02/14/2017 01:00 AM, Brooke Wallace wrote:
>> Hi,
>>
>> I'm curious what the status of RTAI. I see the website was last
>> updated about a year ago, but the latest release notices are dated
>> 2013. Thats ok, maybe its already complete and doesn't need a new
>> release. But I see also on the mail list that kernel patches are still
>> required. Was there ever an effort to have those changes up-streamed
>> into the kernel
>>
>> W'ere thinking about taking a look at RTAI for our RTOS in a project
>> and I want to make sure there is still an active community. Some of
>> the documentation also talks about x86... is there support for ARM?
>>
>> If your no longer using RTAI, what is the popular choice for
>> Linux/RTOS combination now?
>>
>> Please let me know. I was hooked on RTLinux back in the day and would
>> like to get back to some RT development again.
>>
>> -Brooke
>>
>>
>> _______________________________________________
>> Rtai mailing list
>> [email protected]
>> https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai
>
>
>
>
> _______________________________________________
> Rtai mailing list
> [email protected]
> https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai
>
_______________________________________________
Rtai mailing list
[email protected]
https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai