Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zephyr 3.x Support #33

Open
rincewound opened this issue Jun 6, 2023 · 3 comments
Open

Zephyr 3.x Support #33

rincewound opened this issue Jun 6, 2023 · 3 comments

Comments

@rincewound
Copy link

Hey there, are there any plans for to support newer Zephyr versions?
If not: Is there an idea about the scope of work, that would need to be done to support 3.x? While I have somewhat limited time I'd be glad to help.

@tylerwhall
Copy link
Owner

I wrote and am supporting this for my company, so it's going to stay maintained, but we're still on 2.x. I haven't made the separate effort for 3.x since I don't have a reason to test it thoroughly and I still have to maintain 2.x for a while. I want us to upgrade eventually, but it's not currently being worked on.

I imagine there will be some CMake differences in how modules work. And gen_syscalls.py which was forked from Zephyr needs to be updated if the way they generate syscall headers has changed. Then it's just porting to new syscall APIs used mostly by zephyr-core.

I'd appreciate someone taking a look.

More info about support here:
#30

@rincewound
Copy link
Author

Thanks for getting back. I'll look into it.

@jgreenbaum
Copy link

Pull request #43 appears to address the gen_syscalls.py issue with newer Zephyrs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants