Date: Tue, 19 Dec 2023 13:28:00 +0400 From: Maxim V Filimonov <che@bein.link> To: Jan Beich <jbeich@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: security/libfprint: any updates? Message-ID: <11b0c812-1a73-4a0a-ac92-c32ca794dffe@bein.link> In-Reply-To: <msu7-0xu7-wny@FreeBSD.org> References: <cbe0ef50-d768-4254-8d36-2b2c98316908@bein.link> <msu7-0xu7-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, but not really. See, the Linux SPI implementation is (probably) really different, so that would require a reimplementation of SPI in the library which is not the best solution, as you would probably agree. My thinking is "remove SPI support altogether by removing certain supported devices", but it didn't work immediately and requires some more hacking. I patched the meson.build file so that it doesn't contain the spi devices, but that didn't help so it requires further work. On 19.12.2023 05:45, Jan Beich wrote: > Maxim V Filimonov <che@bein.link> writes: > >> Hello, >> >> I'm trying to build new-ish versions of libfprint on FreeBSD >> (probably, that could result in an update to the port as well), but I >> encountered a problem: >> >> ../libfprint/fpi-spi-transfer.c:22:10: fatal error: >> 'linux/spi/spidev.h' file not found >> #include <linux/spi/spidev.h> >> ^~~~~~~~~~~~~~~~~~~~ > Perhaps <sys/spigenio.h> as documented in spigen(4) manpage. Neither > linuxulator nor ports/ tree have examples how to translate SPI_IOC_MESSAGE > into SPIGENIOC_TRANSFER or similar. However, spi(8) can probably help both > debugging and learning the API. > > Disclaimer: I don't use this port and not familar with SPI. -- wbr, Maxim Filimonov <che@bein.link>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11b0c812-1a73-4a0a-ac92-c32ca794dffe>