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/
Fixed some compiler warnings.
New wiringPi version mechanism.
Put 4800 baud (back) into the system.
Re-added piBoardRev (really an alias of piGpioLayout())
for kernels 4.8 onwards.
Some very old stuff might break.
Additional fixes for the ISR code and some tweaks here and
there. I've removed the checks for some operations that might
fail when using the gpiomem interface - which is now the default
way of doing things - if your program segfaults, then you
may need to use sudo on it.