-
Notifications
You must be signed in to change notification settings - Fork 444
Remove unsupported GPIO file system access method #3112
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
Conversation
|
Website deployed to CF Pages, 👀 preview link https://06a21e5c.balenacloud-docs.pages.dev |
Additionally removed commented section on GPIO pins
f77cc0c to
78e0a98
Compare
acostach
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
|
For future reference, the Balena folks may find "A history of GPIO usage on Raspberry Pi devices, and current best practices" at https://pip.raspberrypi.com/categories/685-whitepapers-app-notes-compliance-guides a useful resource. |
|
BTW I see that this page also says "We recommend [Pi Pins][pi-pins] for node.js projects" but according to https://www.npmjs.com/package/pi-pins it was last published 11 years ago (!) and it also uses sysfs, so it'll stop working on newer Linux kernels. |
|
@lurch What's the current recommendation for Node.js projects from Raspberry Pi |
|
@vipulgupta2048 I've got no idea; I don't think that Node.js is something that any of the Raspberry Pi Engineers have looked at. |
|
Yeah something based on libgpiod would be best supported, as long as it’s the correct version (shame that they didn’t get the api right the first time!) |
Additionally removed commented section on GPIO pins