Bartosz Gołaszewski
Bartosz Gołaszewski
> > One last thing before I do, I wanted to touch base on `gpiod/__init__.py` > > Currently, there are a number of "unused" imports. My _guess_ is that this...
Can you elaborate? Not sure how that's useful for online documentation?
> It is not, but it is for offline use. Not everybody depends (or wants to depend) on online docs, and given its a feature already built in to ReadTheDocs,...
Hmm maybe I need to improve the docs a bit. In general you want to run: ``` tar -xvf libgpiod-2.2.1.xz cd ./libgpiod-2.2.1 ./configure make sudo make install ```
I cannot help you if you don't at least post the output of `configure`.
Please follow the guide from https://libgpiod.readthedocs.io/en/latest/contributing.html. Add a proper commit message, use imperative mode in the description and send the patch to the linux-gpio mailing list. Thanks!
Ok so I admit I'm not quite clear on why we need to drop support for v3.9 if nothing changes in the libgpiod code? Is there anything we can actually...
I think you've become the unofficial maintainer of the python bindings by now, I'll defer to your judgement here. I'm fine either way. I really like the type naming improvements...
I need more info, strace logs, the exact code you're running, what the error is etc.
So I'm running the same board and getting this: ``` [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd030] [ 0.000000] Linux version 6.17.0-rc3-next-20250825 (brgl@brgl-build) (aarch64-linux-gnu-gcc (Ubuntu 14.2.0-19ubuntu2) 14.2.0, GNU...