If you can point out what that should say, I'll be happy to update the document, I wrote it quite some time ago but it took a long time to get from writing to release.tbf to Raspberry Pi, I don't think they can be expected to know about all of the forks made by the community. I mean, even in the A history of GPIO usage on Raspberry Pi devices, and current best practices document it's stated that GrazerComputerClub/WiringPi is the currently maintained version. It hasn't seen an update in over a year, while WiringPi/WiringPi is 144 commits and a full major version ahead.... the existence of community maintained translation layers.
Maybe I can shed some light onto this topic:
The document correctly refers to WiringPi/WiringPi and to the developer group
GrazerComputerClub. There is nothing wrong with that. - The first links to the Source Repository, the second the organization unit that took over maintainership.
I' m not happy with
.Due to the underlying hardware changes on Raspberry Pi 5, Wiring Pi does not yet work on this device. For this reason, it is not yet recommended for new projects. WiringPi in fact is actively developed, so more recent versions may work on RaspberryPi 5
This is incorrect — the Raspberry Pi 5 is functional, even with the hardware changes. It’s not a matter of “may work” — it does work!
It doesn’t just restore previous functionality; new features are actively being added. For example, the ISR/event-driven functions have been rewritten. As of version 3.16, the library now supports Kernel Interface V2, which includes debouncing support for GPIO programming tools. It’s currently the fastest and most advanced GPIO library available.
Also, the obsession with the "original developer" - yes, Gordon created WiringPi and he did a great job. Now, for whatever reason he is not in a position to continue his work on the project - this is a great example on how OSS can thrive even after the "original developer"(s) left the project.
Statistics: Posted by evil — Wed Jun 11, 2025 2:24 pm