This is a general tidyup to detach this fork better from Gordon, who was (and perhaps still is) completely inundated with WiringPi-related support questions.
This changeset includes a number of tweaks which should reduce support burden on Gordon. I believe they are essential if we plan to release a new debian package.
They should - hopefully - not reduce or make ambiguous the origins of this code while achieving the above.
* Remove Gordon's email address from all source files to avoid support queries finding their way to him
* Update wiringPi URLs to the GitHub repository to try and keep bugs/issues within the fork
* Bump version to 2.70 ready for a debian package release
* Update debian package maintainer info, add bugs & homepage URLs to this repository
* Changes to support the Zero 2 W (model type 18|0x12)
* Increment version in version.h
* Increment version in debian-template/wiringPi/DEBIAN/control
* Increment version in VERSION as well - I keep missing places where this number is defined
* Increment VERSION_MINOR, missed in previous commits; add missing Pi Z2W model name to piModelNames
Co-authored-by: schwartz <pi@schwartz>
Co-authored-by: PumpkinPi <jack@mirkwood.net>
A recent compiler complains about the sprintf() in authenticate() being able to
write up to 1023 bytes into challenge, which is not possible given that getChallenge()
returns a string 10 bytes smaller than whatever string is in its 1024 byte buffer.
Reducing the size of the buffer in getChallenge() quiets the warning. It should not
affect anything else, as the challenge string is used as a salt that must be <= 96 bits.
This may exist in most cases, but occasionally it does not and it aligns with the way the man page directory is pre-created as well.
Signed-off-by: MichaIng <micha@dietpi.com>
If `pthread_create` fails, `newPin` will never get reset to -1 and process would hang. This change will return from `softPwmCreate` immediately if `pthread_create` returns a non-zero value and avoid hanging forever.
wiringPi.c:1328:21: warning: ‘digitalWrite8Dummy’ defined but not used [-Wunused-function]
1328 | static void digitalWrite8Dummy (UNU struct wiringPiNodeStruct *node, UNU int pin, UNU int value) { return ; }
| ^~~~~~~~~~~~~~~~~~
wiringPi.c:1327:21: warning: ‘digitalRead8Dummy’ defined but not used [-Wunused-function]
1327 | static unsigned int digitalRead8Dummy (UNU struct wiringPiNodeStruct *node, UNU int UNU pin) { return 0 ; }
| ^~~~~~~~~~~~~~~~~
The related nodes at line 1360 and 1362 have been commented before.
Signed-off-by: MichaIng <micha@dietpi.com>
With Gordon ending development of WiringPi, this repository needs to reflect the situation accurately and differentiate between Gordon's final code release and updates made since then.
Now that the upstream maintainer has abandoned this project without
establishing another maintainer, its difficult to choose an appropriate
version number. Going with 2.60 for now, as this only has incremental
changes to support 4B.
Based on this raspi-gpio commit[1] the 2711 chip uses a different method
for pull up/down. This change implements that same method.
With this change, wiringPi now works for the Pi4B with the subset of
functionality used by zynthian.
[1] 80fa7d04ea?diff=unified
This change make the following commands correctly detect the 4B
however there may be an issue with reading GPIO inputs on the 4B
as they are always returning zero.
The aim of this change is to be the source-equivalent of the binary
package release 2.52[1] which was the last release before upstream
development ceased.
[1] http://wiringpi.com/wiringpi-updated-to-2-52-for-the-raspberry-pi-4b/