RFC: Zephyr RTOS Support

[yashi]

Hello,

I have been working with Zephyr and cFS/cFE for quite a while, and I have recently started porting OSAL again so that it can meet the licensing and other requirements for upstream inclusion.

Since porting OSAL to a new operating system is a fairly large change, I assume maintainers would prefer not to review it as a single large PR with many commits.

What would be the best way to structure this work for review?

Questions:

1. Would you accept a Zephyr RTOS port of OSAL?
2. Would you prefer a single PR with many commits, or a series of smaller PRs merged incrementally?

[digitalnumeric]

What is the time frame for having a Zephyr port of the OSAL?

[dzbaker]

Hi @yashi and @digitalnumeric. We don't currently have Zephyr support on the roadmap. We would accept a working/tested Zephyr port. Our team is small, so we're limited in the number of things we can review, so a well-documented port with tests would aid in being able to review/integrate it.

[yashi]

https://github.com/yashi/osal-zephyr/commits/add-zephyr-support/ is what I ment. I don't know how you want PR to be

1. One large PR with everything in it
2. Small PRs with a few commits. Incremental.

I know the maintainers are busy, but if anybody is interested in, here is a Zephyr T2 repot for testing the OSAL port.
https://github.com/yashi/osal-zephyr-sample

[dzbaker]

Going to convert this to a GitHub discussion so this can more easily be discussed.