From: Martin Kepplinger <martin.kepplinger@ginzinger.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tslib: needs kernel headers 3.12
Date: Wed, 25 Jan 2017 10:24:59 +0100 [thread overview]
Message-ID: <aca25d05-0dd2-cb1c-87bf-4475e18991e4@ginzinger.com> (raw)
In-Reply-To: <87r33xsv2y.fsf@dell.be.48ers.dk>
On 2017-01-20 14:46, Peter Korsgaard wrote:
>>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
>
> Hi,
>
> >> Isn't this a bit annoying for people using tslib on kernel olders than
> >> 3.12 ? Isn't there a simpler patch to tslib to avoid depending on
> >> headers >= 3.12 ?
>
> > The present build failure seems to be easy to fix by skipping the ts_uinput
> > tool on pre 3.12 kernels. But since upstream explicitly states that 3.12 is
> > the oldest supported kernel (see commit message link) we are on our own here.
>
> I had the same idea originally, but as it isn't completely nontrivial to
> disable the new code and against the wishes of upstream I decided to
> leave that work for people needing it on pre-3.12 kernels.
>
> With that said, if upstream isn't interested in integrating such a patch
> then it isn't really nice having to carry it in Buildroot either.
>
I (as the upstream maintainer) would happily take a patch that brings
back support for old kernels. plugins/input-raw and tools/ts_uinput
should be affected as they use multitouch.
Simply properly disabling them during configure would be an acceptable
first step to have as a requirement for old kernels.
A github pull request or a patch here would be equally fine with me and
I'd be happy to have it in version 1.4.
prev parent reply other threads:[~2017-01-25 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 12:50 [Buildroot] [PATCH] tslib: needs kernel headers 3.12 Baruch Siach
2017-01-19 14:03 ` Peter Korsgaard
2017-01-20 0:26 ` Thomas Petazzoni
2017-01-20 3:35 ` Baruch Siach
2017-01-20 13:46 ` Peter Korsgaard
2017-01-25 9:24 ` Martin Kepplinger [this message]
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=aca25d05-0dd2-cb1c-87bf-4475e18991e4@ginzinger.com \
--to=martin.kepplinger@ginzinger.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.