Re: Bug#861455: ITP: xf86-input-tslib -- X.org input driver for tslib

[Martin Kepplinger <martink@posteo.de>]

Am 2017-04-29 um 16:29 schrieb Julien Cristau:
> On Sat, Apr 29, 2017 at 12:47:29 +0200, Martin Kepplinger wrote:
> 
>> Package: wnpp
>> Severity: wishlist
>> Owner: Martin Kepplinger <martink@posteo.de>
>>
>> * Package name    : xf86-input-tslib
>>   Version         : 0.0.7
>>   Upstream Author : Martin Kepplinger <martink@posteo.de>
>> * URL             : https://github.com/merge/xf86-input-tslib
>> * License         : MIT
>>   Programming Lang: C
>>   Description     : X.org input driver for tslib
>>
>> xf86-input-tslib had been in Debian before, see
>> https://tracker.debian.org/pkg/xf86-input-tslib and I'm rewriting the
>> packaging completely due to it's age. I only intend to build upon the
>> old changelog file.
>>
>> Former upstream site:
>> http://public.pengutronix.de/software/xf86-input-tslib/
>>
>> Packaging is done here now:
>> https://github.com/merge/xf86-input-tslib-debian
>>
>>  - why is this package useful/relevant?
>>
>> tslib is still quite widely used in embedded at least. It saw much
>> improvements recently and this package would make tslib available to
>> X servers. xf86-input-tslib 0.0.7 was recently released and makes it
>> usable on recent systems. There are plans for multitouch too.
>>
>>  - how do you plan to maintain it?
>>
>> I reached out to the people from the old packaging repo at
>> http://git.debian.org/?p=collab-maint/xf86-input-tslib.git;a=summary
>> but haven't heard anything. It shouldn't be an issue though, to just
>> maintain this little packaging code on github.
>>
> I don't think we should revive this package in Debian.  There has been
> much effort upstream in the last years to reduce the amount of
> device-specific code in userspace drivers, with things stabilizing
> around the evdev and now libinput drivers.  Why does libinput not
> satisfy your needs, and why can't it be made to?

tslib's purpose (among others) is to have variety of filters to apply to
touch input samples, and screen-calibration (linear transformation).

libinput, as far as I know, doesn't have a filter-stack or mechanism to
chain mathematical filters.

thanks,

                              martin