On 12/14/16 8:52 PM, Carsten Haitzler (The Rasterman) wrote: > weston is not the only wayland compositor. is the the sample/test compositor. > wayalnd does not mean sticking to just what weston does. > > i suspect weston's rdp back-end forces a sw gl stack because it's easier to be > driver agnostic and run everywhere and as you have to read-back pixel data for > transmitting over rdp... why bother with the complexity of actual driver setup > and hw device permissions etc... > > what pekka is saying that it's kind of YOUR job then to make a headless > compositor (base it on weston code or write your own entirely from scratch > etc.), and this headless compositor does return a hw egl context to clients. > it > can transport data to the other server via vnc. rdp or any other method > you like. your headless compositor will get new drm buffers from client when > they display (having rendered using the local gpu) and then transfer tot he > other end. the other end can be a vnc or rdp viewer or a custom app your wrote > for your protocol etc. ... but what you want is perfectly doable with > wayland... but it's kind of your job to do it. that is what virtual-gl would > be. a local headless wayland compositor (for wayland mode) with some kind of > display front end on the other end.
Exactly what I needed to know. Thanks. _______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
