-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Future Directions: Monado #53
Comments
Yes, porting to Monado is the next step. I don't think it would take months. Rewriting in Rust would require first adding Rust build support and bindings glue into Monado - even before getting to the driver itself. It's likely to make things easier in the long run, but I'd probably just port the existing code first. |
I said months, thinking of someone unfamiliar with the code.
I would be lying if I said I didn't mention it because I was interested in figuring that out. |
is there a repo we can track the progress on the rewrite? |
There's nothing yet. I have made a start on porting the driver but it's a body of work. I'll push it to https://gitlab.freedesktop.org/thaytan/monado/-/tree/oculus-rift-cv1 once I have something functional |
OpenHMD has long since become unmaintained.
The future for the original Rift CV1, for those who do still have one, or those who wish to keep the old hardware alive and usable, is in my opinion, to port the code to Monado.
This would be a sizeable investment, that would take months of time for even a build to work.
Though, If you wish to be extra, Do it all in Rust for memory safety.
@thaytan Would you like to pin this issue, to direct any prospective developers into the future.
It seems you also have some desire as well: https://discord.com/channels/556527313823596604/837433069404160061/1246504735658348666
The text was updated successfully, but these errors were encountered: