On Wed, Dec 20, 2023 at 07:22 AM, Dave, N1AI wrote:
On Wed, Dec 20, 2023 at 10:06 AM, Evan Hand wrote:
Does anyone have information on Raspberry Pi's direction?? I have read
that a lack of new developments or updates for the package prompted the
move away from WiringPi.? I do not know enough about the other choices to
make any recommendation.
Based on what was said by the Pi team during the Pi 5 launch, I think libgpiod
is the most prominent replacement for WiringPi.? Rafael said switching over
to it would be easy so I think sooner or later that will be the approach
taken.? Some of the other things Rafael did such using a supported kernel
module for i2c bit banging would reduce the need to have gpio code in the
sbitx build.
--
Regards,
Dave, N1AI
I second Dave's recommendation of libgpiod (). It is open source, actively maintained, and endorsed by the Raspberry Pi team. FWIW, a recent post by the Raspberry Pi team indicates that some of the specs have/will change with the advent of the Pi 5, and libgpiod will track any changes that come along (as well as new hardware such as the Compute Module 5 which will debut in 2024).
And in the context that parts of sBitx code perform hardware-level "bit twiddling," C remains the best language for systems-level programming. I suggest building a hardware abstraction layer (HAL) such that bindings for Python, Rust, etc. would be supported. Farhan mentioned that changes will be forthcoming for software development post-3.0 in 2024, so I'm excited to hear what he has planned going forward.
