Re: Remote display with 3D acceleration using Wayland/Weston

2016-12-15 Thread DRC
On 12/15/16 3:01 AM, Pekka Paalanen wrote: > I assure you, this is a limitation of the RDP-backend itself. Nothing > outside of Weston creates this restriction. > > The current RDP-backed is written to set up and use only the Pixman > renderer. Pixman renderer is a software renderer, and will not

Re: [RFC wayland-protocols] Color management protocol

2016-12-15 Thread Pekka Paalanen
On Mon, 12 Dec 2016 18:18:21 +1100 Graeme Gill wrote: > 2) Expecting color management applications to deal with >configuring the compositor in a platform dependent >way, is expecting far too much. I for one am not >about to add multiple platform dependent back >ends (multiple flav

Re: [RFC wayland-protocols] Color management protocol

2016-12-15 Thread Pekka Paalanen
On Wed, 14 Dec 2016 18:49:14 +1100 Graeme Gill wrote: > Carsten Haitzler (The Rasterman) wrote: > > On Mon, 12 Dec 2016 17:57:08 +1100 Graeme Gill > > said: > > >> Right. So a protocol for querying the profile of each output for its > >> surface > >> is a base requirement. > > > > i tota

Re: Remote display with 3D acceleration using Wayland/Weston

2016-12-15 Thread Pekka Paalanen
On Wed, 14 Dec 2016 11:42:54 -0600 DRC wrote: > But if you run OpenGL applications in Weston, as it is currently > implemented, then the OpenGL applications are either GPU-accelerated or > not, depending on the back end used. If you run Weston nested in a > Wayland compositor that is already GPU

Re: [PATCH wayland] server: use a safer signal type for the wl_resource destruction signals

2016-12-15 Thread Pekka Paalanen
On Wed, 14 Dec 2016 14:41:21 +0200 Pekka Paalanen wrote: > On Mon, 5 Dec 2016 16:20:22 +0100 > Giulio Camuffo wrote: > > > wl_list_for_each_safe, which is used by wl_signal_emit is not really > > safe. If a signal has two listeners, and the first one removes and > > re-inits the second one, it