<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Tue, Jun 28, 2016 at 11:01 AM Erik Jensen <<a href="mailto:rkjnsn@google.com">rkjnsn@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Thu, Jun 23, 2016 at 1:49 PM Adam Jackson <<a href="mailto:ajax@nwnk.net" target="_blank">ajax@nwnk.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The idea has been discussed, but I don't know of anyone actually making<br>
any effort in that direction. And honestly I'd prefer if they didn't.<br>
Xorg so deeply assumes that you're talking to physical hardware that<br>
making it _not_ do so requires intrusive changes. Xwayland began life<br>
as an Xorg driver, and that ended up being kind of a bad plan. I don't<br>
see why dummy/nested would be preferable to Xvfb or Xnest.<br></blockquote><div><br></div></div></div><div dir="ltr"><div class="gmail_quote"><div>I can see why Xwayland might be easier as a separate server, given that it has to interact with Wayland input devices and has the option to forward top-level windows individually to Wayland. Are there any factors that similarly complicate the dummy use case? The dummy driver itself is very simple (even more so with Aaron Plattner's proposed cleanups) and rarely needs updates. In our testing so far, it works quite well.</div></div></div></blockquote><div><br></div><div>More to the point, given that the dummy driver already exists and works fine, what is the objection to bumping the version of RandR it supports? Neither proposed patch requires any of the intrusive changes about which you seem to be worried.</div><div><br></div><div>Thanks. </div></div></div>