[PATCH weston 00/25] A new touchscreen calibrator

[Matt Hoosier]

On Tue, Apr 3, 2018, 08:10 Matt Hoosier <matt.hoosier at gmail.com> wrote:

> On Tue, Apr 3, 2018 at 5:35 AM, Philipp Kerling <pkerling at casix.org>
> wrote:
>
>> > Do you happen to know of a good readymade program that fakes the
>> > presence of a touch input device with uinput? I'd love to test this
>> > series, but current Weston is far ahead of what my embedded devices
>> > will do; so I'm in the position of mostly relying on the desktop for
>> > testing.
>> I'm not sure whether it fits your use case, but you can give mtemu a
>> spin.
>>
> https://gitlab.com/shul/mtemu
>
>
> Thanks. That looks like a really useful program. As it turns out, I ended
> up being able to find some real touch hardware to use. It was ancient stuff
> that required writing a uinput program to translate the old ABS_X/Y-style
> input into modern mtdev representation, but it eventually worked.
>
> The calibration functionality in Pekka's patch series seems to work for
> me. I didn't test out any of the mechanism to spawn an auxiliary program
> that saves the results to disk, but the hot-installed copy of the
> calibration worked.
>
> I did have a little trouble understanding how I can pick-and-choose from
> the client side which touch device should be associated with which output.
> The new weston-touch-calibrator program just prints out a flat list of
> input devices and head names, but doesn't seem to let you do permutations
> of that.
>
> So I ended up having to use a 'mode=off' directive in weston.ini to
> temporarily turn off the main display of my laptop so that the touchscreen
> got pegged to the correct physical output. I have the feeling that I just
> overlooked some aspect of configuration about this.
>

... which is of course the statically set UDev properties that associate an
input device with the Wayland output. Nevermind about this question.


> -Matt
>
>
>>
>>
>>
>> > On Fri, Mar 23, 2018, 09:38 Matt Hoosier <matt.hoosier at gmail.com>
>> > wrote:
>> > > On Fri, Mar 23, 2018 at 9:30 AM, Pekka Paalanen <ppaalanen at gmail.co
>> > > m> wrote:
>> > > > On Fri, 23 Mar 2018 08:46:46 -0500
>> > > > Matt Hoosier <matt.hoosier at gmail.com> wrote:
>> > > >
>> > > >> I am very much in favor of the overall approach on this patch
>> > > series.
>> > > >> I've experienced every single one of the problems described in
>> > > this
>> > > >> summary, and my company currently resorts to maintaining a hacky
>> > > >> out-of-tree calibration tool to paper over these problems.
>> > > >
>> > > > Hi Matt,
>> > > >
>> > > > that is very heartwarming to hear. Is your tool specifically for
>> > > Weston
>> > > > too?
>> > >
>> > > Yes and no. It's not phrased as a patch against the Weston source
>> > > code, but it uses heuristics for determining which output the raw
>> > > /dev/input/* events should be correlated against, and those
>> > > heuristics
>> > > probably would fail if some different compositor happened to be
>> > > running.
>> > >
>> > > >
>> > > > I would be very happy if this proposal fits your needs, and
>> > > certainly
>> > > > interested in hearing where it falls short.
>> > > >
>> > > >
>> > > > Thanks,
>> > > > pq
>> > > >
>> > > >> On Fri, Mar 23, 2018 at 7:00 AM, Pekka Paalanen <ppaalanen at gmail
>> > > .com> wrote:
>> > > >> > From: Pekka Paalanen <pekka.paalanen at collabora.co.uk>
>> > > >> >
>> > > >> > Hi all,
>> > > >> >
>> > > >> > the existing touchscreen calibrator in Weston has several
>> > > problems. This
>> > > >> > proposal intends to solve them all by introducing a new
>> > > protocol
>> > > >> > extension for touchscreen calibration and a new calibrator
>> > > tool.
>> > > >> >
>> > > >> > The benefits of the new tool, which the old tool lacks, are:
>> > > >> >
>> > > >> > - You can unambiguously pick a physical touch device to
>> > > calibrate.
>> > > >> >
>> > > >> > - You can be sure your touch events come only from that
>> > > particular
>> > > >> >   device, and that you cannot miss touch events even if the
>> > > current
>> > > >> >   calibration is horribly wrong.
>> > > >> >
>> > > >> > - You can be sure the calibration window (pattern) is shown on
>> > > the right
>> > > >> >   output with the right coordinates.
>> > > >> >
>> > > >> > - You can unambiguously calibrate even multiple touchscreens
>> > > that are
>> > > >> >   all cloned (showing the same image).
>> > > >> >
>> > > >> > - You get a libinput style calibation matrix instead of the
>> > > >> >   WL_CALIBRATION format which depends on output resolution.
>> > > >> >
>> > > >> > - You can load a new calibration into the compositor without
>> > > playing
>> > > >> >   tricks with udev or restarting the compositor.
>> > > >> >
>> > > >> > There is more discussion about the topic at:
>> > > >> > https://phabricator.freedesktop.org/T7868
>> > > >> >
>> > > >> > This patch series depends on the clone mode series:
>> > > >> > https://patchwork.freedesktop.org/series/32898/
>> > > >> >
>> > > >> > There is a full branch available at:
>> > > >> > https://gitlab.collabora.com/pq/weston/commits/touchcalib-1
>> > > >
>> >
>> > _______________________________________________
>> > wayland-devel mailing list
>> > wayland-devel at lists.freedesktop.org
>> > https://lists.freedesktop.org/mailman/listinfo/wayland-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20180404/120ff8c7/attachment.html>