<div dir="auto"><div><div class="gmail_quote"><div dir="ltr">On Tue, Apr 3, 2018, 08:10 Matt Hoosier <<a href="mailto:matt.hoosier@gmail.com">matt.hoosier@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Apr 3, 2018 at 5:35 AM, Philipp Kerling <span dir="ltr"><<a href="mailto:pkerling@casix.org" target="_blank" rel="noreferrer">pkerling@casix.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>> Do you happen to know of a good readymade program that fakes the<br> > presence of a touch input device with uinput? I'd love to test this<br> > series, but current Weston is far ahead of what my embedded devices<br> > will do; so I'm in the position of mostly relying on the desktop for<br> > testing.<br> </span>I'm not sure whether it fits your use case, but you can give mtemu a<br> spin. <br></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <a href="https://gitlab.com/shul/mtemu" rel="noreferrer noreferrer" target="_blank">https://gitlab.com/shul/mtemu</a></blockquote><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div></div></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">... which is of course the statically set UDev properties that associate an input device with the Wayland output. Nevermind about this question.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>-Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br> <div class="m_-8203921686465852924HOEnZb"><div class="m_-8203921686465852924h5"><br> <br> > On Fri, Mar 23, 2018, 09:38 Matt Hoosier <<a href="mailto:matt.hoosier@gmail.com" target="_blank" rel="noreferrer">matt.hoosier@gmail.com</a>><br> > wrote:<br> > > On Fri, Mar 23, 2018 at 9:30 AM, Pekka Paalanen <<a href="mailto:ppaalanen@gmail.co" target="_blank" rel="noreferrer">ppaalanen@gmail.co</a><br> > > m> wrote:<br> > > > On Fri, 23 Mar 2018 08:46:46 -0500<br> > > > Matt Hoosier <<a href="mailto:matt.hoosier@gmail.com" target="_blank" rel="noreferrer">matt.hoosier@gmail.com</a>> wrote:<br> > > ><br> > > >> I am very much in favor of the overall approach on this patch<br> > > series.<br> > > >> I've experienced every single one of the problems described in<br> > > this<br> > > >> summary, and my company currently resorts to maintaining a hacky<br> > > >> out-of-tree calibration tool to paper over these problems.<br> > > ><br> > > > Hi Matt,<br> > > ><br> > > > that is very heartwarming to hear. Is your tool specifically for<br> > > Weston<br> > > > too?<br> > ><br> > > Yes and no. It's not phrased as a patch against the Weston source<br> > > code, but it uses heuristics for determining which output the raw<br> > > /dev/input/* events should be correlated against, and those<br> > > heuristics<br> > > probably would fail if some different compositor happened to be<br> > > running.<br> > ><br> > > ><br> > > > I would be very happy if this proposal fits your needs, and<br> > > certainly<br> > > > interested in hearing where it falls short.<br> > > ><br> > > ><br> > > > Thanks,<br> > > > pq<br> > > ><br> > > >> On Fri, Mar 23, 2018 at 7:00 AM, Pekka Paalanen <ppaalanen@gmail<br> > > .com> wrote:<br> > > >> > From: Pekka Paalanen <<a href="mailto:pekka.paalanen@collabora.co.uk" target="_blank" rel="noreferrer">pekka.paalanen@collabora.co.uk</a>><br> > > >> ><br> > > >> > Hi all,<br> > > >> ><br> > > >> > the existing touchscreen calibrator in Weston has several<br> > > problems. This<br> > > >> > proposal intends to solve them all by introducing a new<br> > > protocol<br> > > >> > extension for touchscreen calibration and a new calibrator<br> > > tool.<br> > > >> ><br> > > >> > The benefits of the new tool, which the old tool lacks, are:<br> > > >> ><br> > > >> > - You can unambiguously pick a physical touch device to<br> > > calibrate.<br> > > >> ><br> > > >> > - You can be sure your touch events come only from that<br> > > particular<br> > > >> > device, and that you cannot miss touch events even if the<br> > > current<br> > > >> > calibration is horribly wrong.<br> > > >> ><br> > > >> > - You can be sure the calibration window (pattern) is shown on<br> > > the right<br> > > >> > output with the right coordinates.<br> > > >> ><br> > > >> > - You can unambiguously calibrate even multiple touchscreens<br> > > that are<br> > > >> > all cloned (showing the same image).<br> > > >> ><br> > > >> > - You get a libinput style calibation matrix instead of the<br> > > >> > WL_CALIBRATION format which depends on output resolution.<br> > > >> ><br> > > >> > - You can load a new calibration into the compositor without<br> > > playing<br> > > >> > tricks with udev or restarting the compositor.<br> > > >> ><br> > > >> > There is more discussion about the topic at:<br> > > >> > <a href="https://phabricator.freedesktop.org/T7868" rel="noreferrer noreferrer" target="_blank">https://phabricator.freedesktop.org/T7868</a><br> > > >> ><br> > > >> > This patch series depends on the clone mode series:<br> > > >> > <a href="https://patchwork.freedesktop.org/series/32898/" rel="noreferrer noreferrer" target="_blank">https://patchwork.freedesktop.org/series/32898/</a><br> > > >> ><br> > > >> > There is a full branch available at:<br> > > >> > <a href="https://gitlab.collabora.com/pq/weston/commits/touchcalib-1" rel="noreferrer noreferrer" target="_blank">https://gitlab.collabora.com/pq/weston/commits/touchcalib-1</a><br> > > ><br> ><br> </div></div><div class="m_-8203921686465852924HOEnZb"><div class="m_-8203921686465852924h5">> _______________________________________________<br> > wayland-devel mailing list<br> > <a href="mailto:wayland-devel@lists.freedesktop.org" target="_blank" rel="noreferrer">wayland-devel@lists.freedesktop.org</a><br> > <a href="https://lists.freedesktop.org/mailman/listinfo/wayland-devel" rel="noreferrer noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/wayland-devel</a><br> </div></div></blockquote></div><br></div></div> </blockquote></div></div></div>