It was nice knowing Raspberry Pi while they lasted. Going to suck losing something that has changed the homegrown embedded system hobby forever.
It was nice knowing Raspberry Pi while they lasted. Going to suck losing something that has changed the homegrown embedded system hobby forever.
GPIOs are the easy bit. You can get those no issue on x86. It’s I2C and SPI that are the issue with x86. You can get the buses sure, but all the device drivers are Device Tree based. You can’t just throw in Device Tree overlays on x86.
Idk, with I2C if it’s not something that needs a kernel level driver, there usually isn’t a problem with interacting with it from user space, for example basically all RAM RGB controllers are I2C and OpenRGB has no problem with them. I’m pretty sure I’ve only ever used an I2C device tree overlay for an RTC.
Also I2C/SMBus is present everywhere on x86, like some graphics cards expose it through their HDMI ports, even some server motherboards have a header for it; but for GPIO I’m unaware of any motherboards that expose it, so good luck researching the chipset and tracing out the pins.
Only a fraction of it is RTCs. What is in the Pi overlays folder is from everything. Not even all the DT I2C RTCs. There is loads of ADCs, DACs, IO extenders, all sorts.
It’s really annoying you can’t do DT on x86 Linux. It’s a bit of a gap in the platform. It would make Linux ARM based developer’s lives easier.
These should all work without kernel drivers. For example, here’s a user space python library for ADS1*15 ADCs, or Nuvoton MS51 IO Expanders. Unless you need very specific timing or require the kernel to know about it, you shouldn’t need a kernel driver.