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

The GPIO_INTERRUPT_PIN = 25 is no longer valid in recent kernels #34

Open
knob-creek opened this issue Aug 21, 2024 · 3 comments
Open

Comments

@knob-creek
Copy link

Since kernel 6.6 (?), the gpio pins have an offset of 512, so the correct number should be 537, now.

Cf. this bug report concerning the GPIO library

On a side note, the whole of the sysfs based API to GPIO is deprecated, so on the long run, this should be migrated to some GPIO library like lgpio.

@BeanGirlThing
Copy link

Unfortunately I don't think we're gonna get a fix, I've been digging through forks and changes over the last few hours trying to get my PiFaceCAD to work again, but it seems like all libraries that exist were made before the API changes. Rendering the device completely obsolite unless someone has the time to fix the issue.

@knob-creek
Copy link
Author

@BeanGirlThing You can fix this on your own: all you need to do is to change GPIO_INTERRUPT_PIN in interrupts.py to 512 + 25. This will make pifacecommon work again (as long as the sysfs based api stays alive).

@ralfoide
Copy link

ralfoide commented Oct 6, 2024

I've hit the same problem when updating from an RPi1 to RPi4 with my PiFace. I've made a fork with the change to fix the GPIO_INTERRUPT_PIN on recent kernels:
https://github.com/ralfoide/pifacecommon

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