Hi Dave,
Indeed, my main "production" sbitx is still on the Pi4 running Debian 11. But I'm in the process of migrating to the Pi 5 and Debian 12. Just realized we don't need the RTC in the sBitx also... as the Pi 5 comes with it (I just bought the battery case). Strangely enough, it seems we can use a rechargeable battery on the Pi 5, so it will recharge the RTC battery when on!
- Rafael
toggle quoted message
Show quoted text
On 1/2/24 15:00, Dave, N1AI wrote:
On Tue, Jan 2, 2024 at 05:49 AM, Rafael Diniz wrote:
So for now I'm basing my sbitx software for the Pi 5 in the pinctr
software, which is the closest to WiringPi we can get (I tried
libgpiod, but then we'll also need separate code for changing pin
modes...):
I'm working on porting the code right now. My Pi 5 arrived! It is
soooo much faster... loved it.
On Tue, Jan 2, 2024 at 05:54 AM, Rafael Diniz wrote:
Btw, this code could be integrated to Farhan' s code at some
point-? if there is interest - as it will support all Raspberry Pi
versions. But I'll not do userland I2C bit-banging, as in my
current code. Concerning WiringPi on Debian 12 -? my fork already
supports it, just like in Debian 11 (but use my fork! Upstream is
already broken in newer kernels).
I agree with all of the above.? I want sbitx to be using a gpio library that is being actively maintained.? I have mentioned libgpiod earlier because that's what the Pi team talked up during the Pi 5 announcement, but if pinctr is easier to integrate, go for it!? I want sbitx to be using i2c in kernel mode, it's more efficient and easier to maintain because someone else is doing the maintenance.? I want sbitx to be able to work on various new models as they arrive, being on actively supported software makes that easier to happen.? Personally I'm still using Debian 11 but will give 12 another try at some point in the near future.
--
Regards,
Dave, N1AI
