<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Document udev property "WL_OUTPUT"" href="https://bugs.freedesktop.org/show_bug.cgi?id=100707#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Document udev property "WL_OUTPUT"" href="https://bugs.freedesktop.org/show_bug.cgi?id=100707">bug 100707</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>Hi Peter, the patch is fine by me, it tells us where we stand and I can work with that. :-) Reviewed-by: Pekka Paalanen <<a href="mailto:pekka.paalanen@collabora.co.uk">pekka.paalanen@collabora.co.uk</a>> I'm not sure udev is the only place where would want to configure the association. It works fine in my use case, where we have labelled connectors and one has to plug the right thing to the right connector, or it doesn't work at all. But I can also envision a different use case, where you would associate a monitor and a touch device in the compositor's (or system's if such existed) configuration based on their inherent properties like serial numbers. Then the user could plug the monitor to any display connector and the touch device to any USB port, and have them automatically associated. Or would that too be good with udev rules, maybe tagging the input device with a monitor serial number, or something? Unfortunately I don't think udev can do anything with monitors, so the monitor matching must always be done in the compositor. Yeah, the udev property in the doc seems good. I just wonder how one would make a desktop GUI to configure them, but that's another matter.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>