[PATCH weston 00/25] A new touchscreen calibrator
ppaalanen at gmail.com
Wed Apr 4 07:27:57 UTC 2018
On Wed, 04 Apr 2018 00:37:58 +0000
Matt Hoosier <matt.hoosier at gmail.com> wrote:
> 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.
Indeed. There is no runtime way to change the touchscreen/output
associations in Weston, it picks it up from the udev properties on the
touch device. Other DEs may have their ways, but I considered it out of
scope for this protocol extension.
Thank you for testing! I wonder if I can out your Tested-by tag in all
the patches, or maybe some specific patch... like the "clients: add a
new touchscreen calibrator"?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the wayland-devel