Really Nvidia? #40
Rubberazer
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
So, a little rant originated here: Issue
It turns out that Nvidia, moving from kernel version 4.x to 5.x, changed the number of the gpiochip devices and also the line numbers for the GPIOs associated to each of them on the Xavier NXs dev kits, for NO reason whatsoever. This is not the first time they do this kind of thing, like the number of the SPI devices on Orins moving from kernel 5.14 to 5.15.
Now, this had an impact on my gpioSetISRFunc() function that makes use of the standard kernel driver to capture interrupts, I need the kernel for that specific function because capturing interrupts from user space is basically impossible. It is solved now, I sorted it out.
I thought that Mr Torvalds mentioned something about "not breaking user space" a long time ago, turns out that Nvidia don't care about version control or something and changes the name of things because somebody forgot how they were called on the previous version.
What it all means is that if you have a user space application calling the driver via ioctl() and you update the kernel the whole thing will break.
For no improvement whatsoever.
Beta Was this translation helpful? Give feedback.
All reactions