search

till-s / rtems-libbspExt

Library for VME memory probing and other
Other
1 stars 2 forks source link

RTEMS-5 version? #1

Open anjohnson opened 3 years ago

anjohnson commented 3 years ago

Hi Till,

Have you looked at what it might take to update this code for RTEMS-5 at all?

The new EPICS port for RTEMS-5 will be using the Posix APIs for the regular threads, semaphores and so on, but I don't know if the APIs that this code is using will need to change at all. Any help or hints you can provide on how to go about updating this code would be most welcome.

Thanks,

till-s commented 3 years ago

Hi Andrew.

I haven't looked at it yet. Would that something I could address during the codeathon?

Best regards

On 2/16/21 12:49 AM, Andrew Johnson wrote:

Hi Till,

Have you looked at what it might take to update this code for RTEMS-5 at all?

The new EPICS port for RTEMS-5 will be using the Posix APIs for the regular threads, semaphores and so on, but I don't know if the APIs that this code is using will need to change at all. Any help or hints you can provide on how to go about updating this code would be most welcome.

Thanks,

  • Andrew

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/till-s/rtems-libbspExt/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD7HTCET3SP3MQIEZL7NHCLS7GXINANCNFSM4XVPO2EQ.

anjohnson commented 3 years ago

Hi Till,

On Feb 16, 2021, at 1:20 AM, till-s notifications@github.com<mailto:notifications@github.com> wrote:

Hi Andrew.

I haven't looked at it yet. Would that something I could address during the codeathon?

Best regards

Definitely, that would be great. The others who have been working on the RTEMS-5 port of EPICS should be at the Codeathon too (as will Gedare Bloom and some of his students), and it would be helpful if you were willing to take a look at the associated PRhttps://github.com/epics-base/epics-base/pull/105 during or before it as well.

I wonder whether it might make sense to pull the libbspExt code into our libCom routines instead of keeping it as a separate module that is neither EPICS nor RTEMS, but that would be for you to offer since I’m not sure what license it uses or if you want to keep it separate.

Thanks,

On 2/16/21 12:49 AM, Andrew Johnson wrote:

Hi Till,

Have you looked at what it might take to update this code for RTEMS-5 at all?

The new EPICS port for RTEMS-5 will be using the Posix APIs for the regular threads, semaphores and so on, but I don't know if the APIs that this code is using will need to change at all. Any help or hints you can provide on how to go about updating this code would be most welcome.

Thanks,

  • Andrew

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/till-s/rtems-libbspExt/issues/1#issuecomment-779640405, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABJTQJ4RPNEV7JRHANLOTXLS7IMCDANCNFSM4XVPO2EQ.

-- Complexity comes for free, simplicity you have to work for.