wayland-devel  

Messages by Thread

• identifying active application/window under wayland Dan Kortschak
  • Re: identifying active application/window under wayland Marius Vlad
  • Re: identifying active application/window under wayland Dan Kortschak
• The Compositor Modules are released, the modular C++ library for writing Wayland compositors Roman Gilg
• [RFC PATCH v4 00/42] Color Pipeline API w/ VKMS Harry Wentland
  • [RFC PATCH v4 01/42] drm: Don't treat 0 as -1 in drm_fixp2int_ceil Harry Wentland
  • Re: [RFC PATCH v4 01/42] drm: Don't treat 0 as -1 in drm_fixp2int_ceil Melissa Wen
  • [RFC PATCH v4 03/42] drm: Correctly round for fixp2int_round Harry Wentland
  • Re: [RFC PATCH v4 03/42] drm: Correctly round for fixp2int_round Pekka Paalanen
  • [RFC PATCH v4 05/42] drm/vkms: Create separate Kconfig file for VKMS Harry Wentland
  • Re: [RFC PATCH v4 05/42] drm/vkms: Create separate Kconfig file for VKMS Melissa Wen
  • [RFC PATCH v4 06/42] drm/vkms: Add kunit tests for VKMS LUT handling Harry Wentland
  • Re: [RFC PATCH v4 06/42] drm/vkms: Add kunit tests for VKMS LUT handling Arthur Grillo
  • Re: [RFC PATCH v4 06/42] drm/vkms: Add kunit tests for VKMS LUT handling Harry Wentland
  • Re: [RFC PATCH v4 06/42] drm/vkms: Add kunit tests for VKMS LUT handling Pekka Paalanen
  • [RFC PATCH v4 07/42] drm/vkms: Avoid reading beyond LUT array Harry Wentland
  • Re: [RFC PATCH v4 07/42] drm/vkms: Avoid reading beyond LUT array Melissa Wen
  • [RFC PATCH v4 09/42] drm/colorop: Introduce new drm_colorop mode object Harry Wentland
  • Re: [RFC PATCH v4 09/42] drm/colorop: Introduce new drm_colorop mode object Melissa Wen
  • [RFC PATCH v4 04/42] drm/vkms: Round fixp2int conversion in lerp_u16 Harry Wentland
  • [RFC PATCH v4 12/42] drm/colorop: Add BYPASS property Harry Wentland
  • [RFC PATCH v4 18/42] drm/vkms: Add kunit tests for linear and sRGB LUTs Harry Wentland
  • [RFC PATCH v4 14/42] drm/colorop: Add atomic state print for drm_colorop Harry Wentland
  • [RFC PATCH v4 10/42] drm/colorop: Add TYPE property Harry Wentland
  • Re: [RFC PATCH v4 10/42] drm/colorop: Add TYPE property Pekka Paalanen
  • Re: [RFC PATCH v4 10/42] drm/colorop: Add TYPE property Simon Ser
  • Re: [RFC PATCH v4 10/42] drm/colorop: Add TYPE property Pekka Paalanen
  • [RFC PATCH v4 16/42] drm/colorop: Add NEXT to colorop state print Harry Wentland
  • [RFC PATCH v4 17/42] drm/vkms: Add enumerated 1D curve colorop Harry Wentland
  • Re: [RFC PATCH v4 17/42] drm/vkms: Add enumerated 1D curve colorop Pekka Paalanen
  • [RFC PATCH v4 22/42] drm/vkms: Use s32 for internal color pipeline precision Harry Wentland
  • Re: [RFC PATCH v4 22/42] drm/vkms: Use s32 for internal color pipeline precision Pekka Paalanen
  • [RFC PATCH v4 28/42] drm/amd/display: Ignore deprecated props when plane_color_pipeline set Harry Wentland
  • [RFC PATCH v4 11/42] drm/colorop: Add 1D Curve subtype Harry Wentland
  • [RFC PATCH v4 19/42] drm/colorop: Introduce DRM_CLIENT_CAP_PLANE_COLOR_PIPELINE Harry Wentland
  • [RFC PATCH v4 15/42] drm/plane: Add COLOR PIPELINE property Harry Wentland
  • [RFC PATCH v4 27/42] drm/colorop: define a new macro for_each_new_colorop_in_state Harry Wentland
  • [RFC PATCH v4 13/42] drm/colorop: Add NEXT property Harry Wentland
  • [RFC PATCH v4 29/42] drm/amd/display: Add bypass COLOR PIPELINE Harry Wentland
  • [RFC PATCH v4 25/42] drm/vkms: Add tests for CTM handling Harry Wentland
  • Re: [RFC PATCH v4 25/42] drm/vkms: Add tests for CTM handling Pekka Paalanen
  • [RFC PATCH v4 26/42] drm/colorop: pass plane_color_pipeline client cap to atomic check Harry Wentland
  • [RFC PATCH v4 30/42] drm/amd/display: Skip color pipeline initialization for cursor plane Harry Wentland
  • [RFC PATCH v4 24/42] drm/tests: Add a few tests around drm_fixed.h Harry Wentland
  • Re: [RFC PATCH v4 24/42] drm/tests: Add a few tests around drm_fixed.h Pekka Paalanen
  • [RFC PATCH v4 37/42] drm/amd/display: Add support for BT.709 and BT.2020 TFs Harry Wentland
  • [RFC PATCH v4 21/42] drm/vkms: Pull apply_colorop out of pre_blend_color_transform Harry Wentland
  • [RFC PATCH v4 34/42] drm/colorop: Add PQ 125 EOTF and its inverse Harry Wentland
  • [RFC PATCH v4 39/42] drm/amd/display: add shaper and blend colorops for 1D Curve Custom LUT Harry Wentland
  • [RFC PATCH v4 31/42] drm/amd/display: Add support for sRGB EOTF in DEGAM block Harry Wentland
  • Re: [RFC PATCH v4 31/42] drm/amd/display: Add support for sRGB EOTF in DEGAM block Melissa Wen
  • Re: [RFC PATCH v4 31/42] drm/amd/display: Add support for sRGB EOTF in DEGAM block Melissa Wen
  • [RFC PATCH v4 20/42] drm/colorop: Add 3x4 CTM type Harry Wentland
  • [RFC PATCH v4 33/42] drm/amd/display: Add support for sRGB EOTF in BLND block Harry Wentland
  • [RFC PATCH v4 02/42] drm: Add helper for conversion from signed-magnitude Harry Wentland
  • Re: [RFC PATCH v4 02/42] drm: Add helper for conversion from signed-magnitude Melissa Wen
  • [RFC PATCH v4 35/42] drm/amd/display: Enable support for PQ 125 EOTF and Inverse Harry Wentland
  • [RFC PATCH v4 23/42] drm/vkms: add 3x4 matrix in color pipeline Harry Wentland
  • Re: [RFC PATCH v4 23/42] drm/vkms: add 3x4 matrix in color pipeline Pekka Paalanen
  • [RFC PATCH v4 36/42] drm/colorop: add BT2020/BT709 OETF and Inverse OETF Harry Wentland
  • [RFC PATCH v4 41/42] drm/colorop: Add mutliplier type Harry Wentland
  • Re: [RFC PATCH v4 41/42] drm/colorop: Add mutliplier type Melissa Wen
  • [RFC PATCH v4 42/42] drm/amd/display: add multiplier colorop Harry Wentland
  • [RFC PATCH v4 40/42] drm/amd/display: add 3x4 matrix colorop Harry Wentland
  • [RFC PATCH v4 08/42] drm/doc/rfc: Describe why prescriptive color pipeline is needed Harry Wentland
  • Re: [RFC PATCH v4 08/42] drm/doc/rfc: Describe why prescriptive color pipeline is needed Pekka Paalanen
  • [RFC PATCH v4 38/42] drm/colorop: Add 1D Curve Custom LUT type Harry Wentland
  • [RFC PATCH v4 32/42] drm/amd/display: Add support for sRGB Inverse EOTF in SHAPER block Harry Wentland
  • Re: [RFC PATCH v4 00/42] Color Pipeline API w/ VKMS Joshua Ashton
  • Re: [RFC PATCH v4 00/42] Color Pipeline API w/ VKMS Harry Wentland
  • Re: [RFC PATCH v4 00/42] Color Pipeline API w/ VKMS Daniel Vetter
  • Re: [RFC PATCH v4 00/42] Color Pipeline API w/ VKMS Joshua Ashton
  • Re: [RFC PATCH v4 00/42] Color Pipeline API w/ VKMS Melissa Wen
  • Re: [RFC PATCH v4 00/42] Color Pipeline API w/ VKMS Melissa Wen
  • Re: [RFC PATCH v4 00/42] Color Pipeline API w/ VKMS Harry Wentland
  • Re: [RFC PATCH v4 00/42] Color Pipeline API w/ VKMS Melissa Wen
• waypipe not working Colin Rudakiewicz
  • Re: waypipe not working Michel Dänzer
  • RE: waypipe not working Colin Rudakiewicz
  • Re: waypipe not working Michel Dänzer
• Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Marius Vlad
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston David Edmundson
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Pekka Paalanen
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Pekka Paalanen
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Pekka Paalanen
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Pekka Paalanen
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Pekka Paalanen
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Pekka Paalanen
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Pekka Paalanen
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Pekka Paalanen
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Terry Barnaby
  • Re: Wayland debugging with Qtwayland, gstreamer waylandsink, wayland-lib and Weston Marius Vlad
• why not flow control in wl_connection_flush? jleivent
  • Re: why not flow control in wl_connection_flush? Olivier Fourdan
  • Re: why not flow control in wl_connection_flush? jleivent
  • Re: why not flow control in wl_connection_flush? Pekka Paalanen
  • Re: why not flow control in wl_connection_flush? jleivent
  • Re: why not flow control in wl_connection_flush? Pekka Paalanen
  • Re: why not flow control in wl_connection_flush? jleivent
  • Re: why not flow control in wl_connection_flush? Pekka Paalanen
  • Re: why not flow control in wl_connection_flush? jleivent
  • Re: why not flow control in wl_connection_flush? Pekka Paalanen
  • Re: why not flow control in wl_connection_flush? jleivent
  • Re: why not flow control in wl_connection_flush? Pekka Paalanen
  • Re: why not flow control in wl_connection_flush? jleivent
• 2024 X.Org Board of Directors Elections Nomination period is NOW Christopher Michael
  • 2024 X.Org Board of Directors Elections timeline extended, request for nominations Christopher Michael
  • Reminder: 2024 X.Org Board of Directors Elections timeline extended, request for nominations Christopher Michael
  • Re: Reminder: 2024 X.Org Board of Directors Elections timeline extended, request for nominations Christopher Michael
  • 2024 X.Org Foundation Membership deadline for voting in the election Christopher Michael
  • Re: 2024 X.Org Foundation Membership deadline for voting in the election Ricardo Garcia
  • Re: 2024 X.Org Foundation Membership deadline for voting in the election Marc Balmer
  • Re: 2024 X.Org Foundation Membership deadline for voting in the election Pekka Paalanen
  • Re: 2024 X.Org Foundation Membership deadline for voting in the election Laurent Pinchart
• Issue with logind-launcher Akshaya Maran
  • Re: Issue with logind-launcher Marius Vlad
• 2024 X.Org Foundation Membership deadline for voting in the election Christopher Michael
• Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values Pekka Paalanen
  • Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values Tomi Valkeinen
  • Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values Marius Vlad
  • Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values Daniel Stone
  • Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values Tomi Valkeinen
  • Re: [PATCH 1/2] drm/tidss: Fix initial plane zpos values Daniel Stone
• Touchpad on Lenovo Legion 9 16IRX8 (not working) Mateusz K
• [ANNOUNCE] libei 1.2.1 Peter Hutterer
• Punch hole logic in gl-renderer in weston Namit Solanki (QUIC)
  • Re: Punch hole logic in gl-renderer in weston Marius Vlad
• Bug in the keyboard when using Wayland. j...@lerena.pro
  • Re: Bug in the keyboard when using Wayland. Simon Zeni
• [ANNOUNCE] wayland-protocols 1.33 Daniel Stone
• Right mailing list for mutter/gnome-remote-desktop question? Matt Hoosier
  • Re: Right mailing list for mutter/gnome-remote-desktop question? Daniel Stone
  • Re: Right mailing list for mutter/gnome-remote-desktop question? Neal Gompa
• Questions about mmonitor Igor Korot
• [ANNOUNCE] libinput 1.25.0 José Expósito
• [PATCH] scanner.c: prefer strchr() over for loop and toupper() in place James Tirta Halim
  • Re: [PATCH] scanner.c: prefer strchr() over for loop and toupper() in place Simon Ser
  • Re: [PATCH] scanner.c: prefer strchr() over for loop and toupper() in place Thiago Macieira
• protocol rules question: is an array arg of object ids legal? jleivent
  • Re: protocol rules question: is an array arg of object ids legal? Simon Ser
  • Re: protocol rules question: is an array arg of object ids legal? jleivent
• Mail regarding how to contribute. Gowreesh Simhadri
• Status of icc profile integration for output devices? Gramer, Markus
  • Re: Status of icc profile integration for output devices? Pekka Paalanen
  • RE: Status of icc profile integration for output devices? Gramer, Markus
• aging merge request jleivent
  • Re: aging merge request Joshua Ashton
  • Re: aging merge request jleivent
• Backport to 9.0.0 of: backend-drm: schedule connector disable for detached head Martin Petzold
  • Re: Backport to 9.0.0 of: backend-drm: schedule connector disable for detached head Marius Vlad
• SEGFAULT encountered in wl_event_queue_release Louis DeLosSantos
• what are the protocol rules about uniqueness of event and request names? jleivent
  • Re: what are the protocol rules about uniqueness of event and request names? David Edmundson
  • Re: what are the protocol rules about uniqueness of event and request names? jleivent
  • Re: what are the protocol rules about uniqueness of event and request names? Sebastian Wick
  • Re: what are the protocol rules about uniqueness of event and request names? jleivent
  • Re: what are the protocol rules about uniqueness of event and request names? Pekka Paalanen
• [ANNOUNCE] libei 1.2.0 Peter Hutterer
• Issues with cursors (cursor-shape-v1) Campbell Barton
  • Re: Issues with cursors (cursor-shape-v1) Simon Ser
  • Re: Issues with cursors (cursor-shape-v1) Campbell Barton
• Introducing xwayland-run, a set of small utilities to run X11 and Wayland clients Olivier Fourdan
  • Re: Introducing xwayland-run, a set of small utilities to run X11 and Wayland clients Simon Ser
  • Re: Introducing xwayland-run, a set of small utilities to run X11 and Wayland clients Olivier Fourdan
  • Re: Introducing xwayland-run, a set of small utilities to run X11 and Wayland clients Martin Stransky
  • Re: Introducing xwayland-run, a set of small utilities to run X11 and Wayland clients Simon Ser
  • Re: Introducing xwayland-run, a set of small utilities to run X11 and Wayland clients Martin Stransky
  • Re: Introducing xwayland-run, a set of small utilities to run X11 and Wayland clients Neal Gompa
  • Re: Introducing xwayland-run, a set of small utilities to run X11 and Wayland clients Pekka Paalanen
  • Re: Introducing xwayland-run, a set of small utilities to run X11 and Wayland clients Olivier Fourdan
• Knowing which parts of an xdg_toplevel are off-screen / occluded Max Ihlenfeldt
• [ANNOUNCE] weston 12.0.3 Marius Vlad
  • Re: [ANNOUNCE] weston 12.0.3 Md Akram
• [ANNOUNCE] weston 13.0.0 Marius Vlad
• registry_bind function call Robert Ayrapetyan
  • Re: registry_bind function call Pekka Paalanen
• [ANNOUNCE] weston 12.0.95 Marius Vlad
• get input device in wayland weinan wang
  • Re: get input device in wayland Peter Hutterer
  • Re:Re: get input device in wayland weinan wang
  • Re: Re: get input device in wayland Peter Hutterer
  • 回复: Re: get input device in wayland WeiWei
  • Re: 回复: Re: get input device in wayland Peter Hutterer
  • Re:Re: 回复: Re: get input device in wayland weinan wang
  • Re: Re: 回复: Re: get input device in wayland Peter Hutterer
  • 回复: Re: 回复: Re: get input device inwayland WeiWei

• Earlier messages
• Later messages