On Thursday, June 29, 2017 1:29:58 PM PDT Rodrigo Vivi wrote:
> Copied from Mesa with no modifications.
>
> Gives us Coffee Lake and Cannon Lake PCI IDs.
>
> Cc: Kenneth Graunke
> Cc: Eric Anholt
> Signed-off-by: Rodrigo Vivi
>
UDL (usb) devices are blacklisted because of they weird behaviour when
it comes to vblank events. As EVDI uses very similar model of handling
vblanks it should be treated similarly.
When doing a page flip, EVDI does not wait for real vblank, but
simulates it by adding constant delay. It also does
I don't understand what we gain by sending the position again in global
compositor space, it will always match the position of the wl_output.
David
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info:
Hi Olivier,
it's very hard for me to wrap my head around this, so the below may
sound a bit harsh, sorry. I don't mean to rant, but I feel there is
something fundamental amiss. I am diving back into the high-level
design which is fairly separated from the xdg_output interface.
On Thu, 6 Jul 2017
This protocol aims at describing outputs in way which is more in line
with the concept of an output on desktop oriented systems.
Some information are more specific to the concept of an output for a
desktop oriented system and may not make sense in other applications,
such as IVI systems for
Hi,
> I don't understand what we gain by sending the position again in global
> compositor space, it will always match the position of the wl_output.
That's right, but the position in wl_output has limited sense for some
applications (basically, an x/y position makes sense only in a 2D
On 2017年07月06日 00:15, Alex Deucher wrote:
On Tue, Jul 4, 2017 at 6:26 AM, zhoucm1 wrote:
On 2017年07月04日 13:43, zhoucm1 wrote:
On 2017年07月04日 13:34, Alex Deucher wrote:
On Tue, Jul 4, 2017 at 1:22 AM, zhoucm1 wrote:
On 2017年07月04日 11:41, Alex
Hi Pekka,
> I think I can offer only mostly mechanical comments, as I am still
> quite confused about how this will actually be used.
Well, for now, it will be used by Xwayland, might be of some interest for other
clients who might need to know about the output "logical" size (e.g. screencast
On Tue, 4 Jul 2017 14:13:43 +0200
Olivier Fourdan wrote:
> This protocol aims at describing outputs in way which is more in line
> with the concept of an output on desktop oriented systems.
>
> Some information are more specific to the concept of an output for a
> desktop