[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180206170013.7e2b08bb@eldfell>
Date: Tue, 6 Feb 2018 17:00:13 +0200
From: Pekka Paalanen <ppaalanen@...il.com>
To: Gerd Hoffmann <kraxel@...hat.com>
Cc: Tomeu Vizoso <tomeu.vizoso@...labora.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
David Airlie <airlied@...ux.ie>,
Stefan Hajnoczi <stefanha@...il.com>,
Jason Wang <jasowang@...hat.com>, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org,
virtualization@...ts.linux-foundation.org, kernel@...labora.com
Subject: Re: [PATCH v3 1/2] drm/virtio: Add window server support
On Mon, 5 Feb 2018 17:03:22 +0100
Gerd Hoffmann <kraxel@...hat.com> wrote:
> On Mon, Feb 05, 2018 at 03:46:17PM +0100, Tomeu Vizoso wrote:
> > On 02/05/2018 01:20 PM, Gerd Hoffmann wrote:
> > > Hi,
> > >
>
> Hmm. I allways assumed the wayland client allocates the buffers, not
> the server. Is that wrong?
Hi Gerd,
a fly-by comment here:
The standard operation mode on Wayland indeed is that the client
allocates any pixel buffers. It is not the whole story though.
Server allocated buffers passed to a client also exist:
- core protocol uses this to pass keymaps to clients
- people are not forbidden from writing Wayland extensions that do this
for whatever reason
The latter server-allocated case could probably be overlooked, but the
keymap case not really. Furthermore, copy&paste and drag&drop protocol
pass pipe file descriptors via Wayland to establish client-to-client
pipes.
Thanks,
pq
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists