On Wed, 2015-06-17 at 14:05 -0700, Jasper St. Pierre wrote:
And yet it's still fast enough. Eliminating roundtrips would be nice,
but we should make sure we're eliminating the roundtrips that matter.
On a 2.3GHz haswell I get about 100k roundtrips per second (measuring
with x11perf -pointer).
On Wed, 2015-06-17 at 16:52 -0700, Keith Packard wrote:
Having the code shared is nice, but the big cost of GL these days is
all of the rendering and shader compiler state. Steaming megabytes of
data for every application. Memory is cheap these days; maybe we
don't care anymore.
There's a
On 06/08/2015 03:14 PM, Siim Põder wrote:
Hi
This was sent to xorg-devel a few years ago. It still applies and still
appears
to work. I resending this because it affects me. Comments or application to
the
tree would be greatly appreciated :)
The motivation for getting this is chrome
On 15 June 2015 at 05:08, Michel Dänzer mic...@daenzer.net wrote:
On 12.06.2015 08:48, Dave Airlie wrote:
We need this for doing USB offload scenarios using glamor
and modesetting driver.
unfortunately only gbm in mesa 10.6 has support for the
linear API.
Signed-off-by: Dave Airlie
Hi
Quoting Aaron Plattner (2015-06-18 15:28:18)
On 06/08/2015 03:14 PM, Siim Põder wrote:
Not that this patch hurts or anything, but is there any particular
reason this remote desktop thing is using Xvfb rather than Xorg +
xf86-video-dummy? I thought there was an effort to kill off the
On 19 June 2015 at 02:02, Emil Velikov emil.l.veli...@gmail.com wrote:
On 15 June 2015 at 05:08, Michel Dänzer mic...@daenzer.net wrote:
On 12.06.2015 08:48, Dave Airlie wrote:
We need this for doing USB offload scenarios using glamor
and modesetting driver.
unfortunately only gbm in mesa
Adam Jackson a...@nwnk.net writes:
Not just that the GC hasn't changed, that it's still valid for the
drawable; window resize will invalidate your composite clip.
Nah, the expense is computing the mask values from the geometry; that's
completely independent of both source and dest, and depends
When an output is disabled via the cmdline, we can use that information
to prevent assigning the current CRTC to the output and free it up for
reuse by other outputs in the first pass of picking CRTC.
Reported-and-tested-by: Nathan Schulte nmschu...@gmail.com
Signed-off-by: Chris Wilson
We perform two passes over the CRTC in order to find the preferred CRTC
for each enabled output. In the first pass, we try to preserve the
existing output - CRTC relationships (to avoid unnecessary flicker).
If that pass fails, we try again but with all outputs first disabled.
However, the logic
