01:15clamps: compositors already have to do a similar mapping for multiple touch screens
07:27wb9688: What can be the cause of "(wf-panel:158300): Gdk-DEBUG: 09:18:01.070: not a valid new object id (4278190089), message toplevel(n)"? This is in a GTK app that has its own code to handle foreign toplevel stuff
07:34wb9688: Fwiw it happens after turning off the monitor, turning it back on, turning it off again, turning it back on again and then opening a toplevel
07:41wb9688: (and it's somewhere in this code: https://github.com/WayfireWM/wf-shell/tree/master/src/panel/widgets/window-list )
07:57MrCooper: one compositor per GPU is possible in principle via DRM leasing, though there can be subtle hardware constraints which might prevent all such compositors from using their desired output configuration at the same time
07:57MrCooper: *per GPU output
09:02pq: Company, FWIW, I do have two GPUs, running my desktop on one, and a separate physical seat with the other for testing weston on DRM from a terminal window. They are not proper desktop sessions. Proper desktops tend to assume that one user can have at most one session.
09:06pq: orowith2os[m], input devices could be easily assigned via physical seats, but the problem is that I think a systemd physical seat requires at least one DRM device assigned to it, and when using DRM leases, that does not exist. But maybe seatd can do things differently and make it happen.
09:09pq: wb9688, re: the seat discussion; physical seats (configured in udev) are not the same thing as Wayland logical seats (wl_seat globals).
09:10wb9688: Yes, I found that out
09:10pq: wb9688, if you had multiple logical seats, they would be sub-sets of the devices in the physical seat.
09:13pq: orowith2os[m], IMO the best architecture would be for seatd to hand out single-output DRM leases per physical seat, and hand out input devices as usual per physical seat. Then you'd simply run any Wayland compositor as usual when you run it on DRM/libinput.
09:13pq: one compositor instance per physical seat
09:14pq: It has no Wayland involved in splitting or arranging the physical seats, no Wayland system compositor. Eaach session compositor handles its leased DRM device and input devices directly, which means there is no intermediate processing having shovel input and output.
09:15wb9688: Yeah
09:17pq: *no intermediate process having to shovel input and output
11:25wlb: weston Issue #808 closed \o/ (unknown child process exited https://gitlab.freedesktop.org/wayland/weston/-/issues/808)
22:02wlb: weston Merge request !1351 opened by Robert Mader (rmader) Draft: pixel-formats: Add P010 format https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1351