From: Benjamin Li <benl@squareup.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org
Subject: Re: [libgpiod,v1.6.x,0/3] build: fix compile issues against non-glibc
Date: Mon, 27 Feb 2023 12:56:36 -0800 [thread overview]
Message-ID: <2e7df47a-f9fc-01a1-2b6b-c1bfb5b153ca@squareup.com> (raw)
In-Reply-To: <CAMRc=McAAT7A9-XM4QdRtr9mFbDNM8bpDNJXUrxxxg6QppmfHw@mail.gmail.com>
On 2/25/23 6:10 AM, Bartosz Golaszewski wrote:
> I applied patch 2/3 as it's a fix. For the rest of them - my goal for
> the v1.6.x series is to not support it anymore, than is absolutely
> necessary - that means no new features and android build looks like
> one to me. Any chance you can carry this locally?
Sure, we don't mind. But I'd like to gently remind that a lot of device
manufacturers like us have platforms that are unfortunately stuck on
older kernel versions that don't have the v2 IOCTLs.
Are there plans to introduce backwards compatibility to libgpiod v2
to support pre-5.10 kernels without v2 IOCTLs? I assume no based on
your talk from July since there's a major data model re-architecture.
Anyways, as an aside it would be nice to note in the README about the
5.10-or-later requirement for libgpiod v2 (apologies if it's mentioned
and I missed it).
I didn't learn about the compatibility gap until I tested libgpiod v2
tools on-device and found that they failed without a sufficiently new
kernel. Bummer as I was looking forward to being able to reference
GPIOs by just the labels in the CLI!
>
> For v2.x I'm open to adding it but have a couple comments, see the
> relevant email threads.
Thanks, will respond there.
Ben
>
> Bart
next prev parent reply other threads:[~2023-02-27 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 3:08 [libgpiod,v1.6.x,0/3] build: fix compile issues against non-glibc Benjamin Li
2023-02-25 3:08 ` [libgpiod,v1.6.x,1/3] tools: use getprogname() when available to remove dependency on glibc Benjamin Li
2023-02-25 3:08 ` [libgpiod,v1.6.x,2/3] core: add missing #include for basename() Benjamin Li
2023-02-25 3:08 ` [libgpiod,v1.6.x,3/3] build: add Android.bp to build within Android tree Benjamin Li
2023-02-25 14:10 ` [libgpiod,v1.6.x,0/3] build: fix compile issues against non-glibc Bartosz Golaszewski
2023-02-27 20:56 ` Benjamin Li [this message]
2023-02-27 21:01 ` Bartosz Golaszewski
2023-02-27 21:15 ` Benjamin Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2e7df47a-f9fc-01a1-2b6b-c1bfb5b153ca@squareup.com \
--to=benl@squareup.com \
--cc=brgl@bgdev.pl \
--cc=linux-gpio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).