Thanks, Quentin, I'll take a look at Jozef's videos as time permits. Getting
lots of time pressure to get something working, and even our SoM vendor
provides examples that modify local.conf... so much for helping us with the
"right" way to do things. I appreciate your advice, and can now see
Hi Scott,
On Mon, Jul 20, 2020 at 10:48:52AM -0700, Scott Whitney wrote:
> Thanks for the tip, Joel. I'm still new to this. How should libgpiod-dev be
> added to my local.conf?
> Do I just need to add it to EXTRA_IMAGE_FEATURES? Do I still need to add
> libgpiod to IMAGE_INSTALL_append?
>
Thanks for the tip, Joel. I'm still new to this. How should libgpiod-dev be
added to my local.conf?
Do I just need to add it to EXTRA_IMAGE_FEATURES? Do I still need to add
libgpiod to IMAGE_INSTALL_append?
Your help is greatly appreciated!
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all
You would need to add libgpiod-dev, presumably, to get the build
requirements.
On Fri, Jul 17, 2020 at 4:23 PM Scott Whitney wrote:
> I should also note that gpioinfo and other tools from libgpiod run as
> expected on the target, and that /usr/lib has libgpiod.so.2
> (libgpiod.so.2.1.1) in it.
I should also note that gpioinfo and other tools from libgpiod run as expected
on the target, and that /usr/lib has libgpiod.so.2 (libgpiod.so.2.1.1) in it.
I would also like the header file to be put into the image so that I can
build/run executables using libgpiod on the target.
I'm using Yocto Warrior 4.19.35 on a Variscite i.MX8M MINI SoM. I need to be
able to respond to some interrupt events on GPIO events from userspace.
I saw on kernel.org that the sysfs ABI is being deprecated, and the
recommendation is to use libgpiod.
