-
Notifications
You must be signed in to change notification settings - Fork 53
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
Add riscv64 bindings #175
Add riscv64 bindings #175
Conversation
I don't think there exists any easily accessible risc-based CI. So... I don't know if we want to include these bindings as a best effort (and make them go outdated frequently) or just advise users to use the |
Hmm, what would make these bindings get outdated I basically run my riscv machine constantly so if I could possibly find a way to check that it would be easy to solve |
New kernels |
Considering this was run on kernel version 5.10 it might already be outdated |
Which is exactly why CI would be nice. Looking at our CI file, we already use QEMU + ubuntu-ports for a bunch of targets anyway and they seem to have a riscv64 target, we just don't generate for that, because nobody cared. Could you try to fix that? |
I can try again, not exactly a ci master |
It's awkward when using Smithay to have to enable this for several different dependencies. It could automatically use that when generated bindings don't already exist, but
The kernel ABI should be stable, so the existing version continues to work, right? I guess it just needs to be regenerated when their are new ioctls/etc that drm-rs adds support for? |
It seems the bindings here are the same as The same DRM headers are used on Linux and BSDs. See in https://github.com/torvalds/linux/blob/master/include/uapi/drm/drm.h the So I think we could just generate one version of the bindings if we manually specify |
158cef0
to
854c05a
Compare
#176 has a possible solution for this, though CI still needs to be updated. |
Closed in favor of #176 |
No description provided.