Hey Jakob,
On Thu, 5 Jul 2018 at 14:32, Jakob Bornecrantz wrote:
> So from a VR compositor getting blocked like this is a no-go as the
> user would quickly throw EPUKE. The situation is compounded by the
> fact that the VR compositor has no idea what the display compositor is
> doing with regards
On Thu, Jul 05, 2018 at 02:32:42PM +0100, Jakob Bornecrantz wrote:
> Hello Daniel² et al,
>
> I apologies in advance if the things I bring up are a bit orthogonal
> to the current discussion. And I'm writing this from the view of VR,
> but I have not written a VR compositor so take my comments wit
Hello Daniel² et al,
I apologies in advance if the things I bring up are a bit orthogonal
to the current discussion. And I'm writing this from the view of VR,
but I have not written a VR compositor so take my comments with a bit
of salt. And also changing modes while using a VR headset is probably
On Wed, Jul 4, 2018 at 5:44 PM, Daniel Stone wrote:
> Hi,
> The atomic API being super-explicit about how userspace sequences its
> calls is great and all, but having shared global state implicitly
> dragged in is kind of ruining my day.
>
> Currently on Intel, Weston sometimes fails on hotplug, b
Hi,
The atomic API being super-explicit about how userspace sequences its
calls is great and all, but having shared global state implicitly
dragged in is kind of ruining my day.
Currently on Intel, Weston sometimes fails on hotplug, because a
commit which only enables CRTC B (not touching CRTC A o
