On Fri, Feb 1, 2019 at 3:43 AM Pekka Paalanen wrote:
>
> On Thu, 31 Jan 2019 12:03:25 -0700
> Chris Murphy wrote:
>
> > I'm pretty sure most every desktop environment and distribution have
> > settled on colord as the general purpose service.
> > https://github.com/hughsie/colord
> >
On Mon, Feb 18, 2019 at 04:28:18PM +, Daniel Stone wrote:
> Hi Simon,
>
> On Mon, 18 Feb 2019 at 16:22, Simon Ser wrote:
> > On Friday, October 26, 2018 11:13 AM, Simon Ser wrote:
> > > Compositors also expose output refresh rate, which shouldn't be used
> > > for synchronization purposes.
Hi Simon,
On Mon, 18 Feb 2019 at 16:22, Simon Ser wrote:
> On Friday, October 26, 2018 11:13 AM, Simon Ser wrote:
> > Compositors also expose output refresh rate, which shouldn't be used
> > for synchronization purposes.
>
> I'd like to bump this patch, because people apparently do use
On Friday, October 26, 2018 11:13 AM, Simon Ser wrote:
> Compositors also expose output refresh rate, which shouldn't be used
> for synchronization purposes.
I'd like to bump this patch, because people apparently do use wl_output's
refresh rate for synchronization purposes in Firefox [1]. I
On 18/02/19 11:02 pm, Daniel Stone wrote:
Hi Scott,
On Mon, 18 Feb 2019 at 03:27, Scott Anderson
wrote:
In the Weston implementation, it's simply a case of the compositor
getting the fence from the client, using eglWaitSyncKHR (or equivilent)
on it, and passing back a release fence from
Hi Scott,
On Mon, 18 Feb 2019 at 03:27, Scott Anderson
wrote:
> In the Weston implementation, it's simply a case of the compositor
> getting the fence from the client, using eglWaitSyncKHR (or equivilent)
> on it, and passing back a release fence from OUT_FENCE_FD.
Yep, that's pretty much the
