Re: What is the next step for RTEMS and EPICS? Does a small (virtual) workshop make sense?

[Chris Johns via Core-talk <core-talk at aps.anl.gov>]

On 5/8/2023 12:48 am, Heinz Junkes wrote:
> Hi Andrew & Chris & Gedare,
> 
> yes, we should definitely meet. I may not be able to be there on the very next Wednesday :-(
> I am giving a class from 2pm to 5pm.
> 
> A lot has happened with RTEMS and EPICS recently. It's been so fast that I haven't kept up with it at all.
> But we should use the momentum now and incorporate what we have achieved into the next release of EPICS.
> 
> I withdraw my PR (https://github.com/epics-base/epics-base/pull/295).
> 
> This week I have intensively tested Chris' PR (https://github.com/epics-base/epics-base/pull/375) 
> on my hardware (MVME6100 and MVME3100). 
> Vijay has made some improvements in the RTEMS kernel which have been included there. 
> I have changed only a few small things in posix/rtems_config.c 
> (e.g. 
> -#define CONFIGURE_MICROSECONDS_PER_TICK 10000
> +#define CONFIGURE_MICROSECONDS_PER_TICK 1000
> )
> which I will then submit collectively.
> 
> I already have the hardware in use with the usual modules:
> asyn, autosave, busy, calc, devlib2, ip, ipac, recsync, seq-2.2.8, sscan
> 
> Everything compiled perfectly. We should please adopt Chris's PR in EPICS right now. 
> This will we'll make a lot of progress.
> 
> I myself will try to integrate the ntpd as a time provider next week and try to create
> documentation for RTEMS6/EPICS7 at the end of August for the Documentathlon. I would also
> have to provide a test for CI?

The last commit on https://github.com/kiwichris/epics-base/tree/rtems-ntpd is
the one to use. I will create a pull request once
https://github.com/epics-base/epics-base/pull/375 is resolved.

> I'm sure I've forgotten a few things. 

I have opened a ticket on libdebugger and Michael has kindly pointed out I
should review what Till has done. I am yet to do this. I have made some progress
on support for PowerPC but nothing I can post.

Chris