On 13 March 2017 at 17:07, Adam Jackson wrote:
> On Fri, 2017-03-10 at 23:23 +, Emil Velikov wrote:
>> > On 10 March 2017 at 16:32, Adam Jackson wrote:
>> > I neither expect nor want this to happen. dummy might have some minor
>> > utility, but the nested driver
On 15/03/17 06:31 PM, Tino Mettler wrote:
> On Wed, Mar 15, 2017 at 18:13:09 +0900, Michel Dänzer wrote:
>> Same problem with fullscreen and windowed?
>
> I can't really tell. The tearing happens in the upper part of the
> screen. When moving the mpv window to the top of the screen, the
>
On 16/03/17 10:24 AM, Eric Anholt wrote:
> We were binding the screen pixmap as the dash and sampling its alpha,
> which is usually just 1.0 (no dashing at all).
>
> Please cherry-pick this to active stable branches.
>
> Signed-off-by: Eric Anholt
> ---
> glamor/glamor_dash.c
Eric Anholt writes:
> We were binding the screen pixmap as the dash and sampling its alpha,
> which is usually just 1.0 (no dashing at all).
>
> Please cherry-pick this to active stable branches.
>
> Signed-off-by: Eric Anholt
Thank you for finding this!
Hello all, been a while since I rang your doorbell, greetings from West
Virginia;
I am in the process of converting an old lathe to cnc, and using a pi 3b
as the driver.
Doing some work on the configuration today, I got curious to see if the
features I was adding to the configuration were
We were binding the screen pixmap as the dash and sampling its alpha,
which is usually just 1.0 (no dashing at all).
Please cherry-pick this to active stable branches.
Signed-off-by: Eric Anholt
---
glamor/glamor_dash.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Mon, 13 Mar 2017, Petri Latvala wrote:
> A new intel-gpu-tools quarterly release is available with the
> following changes:
> Jason Ekstrand (1):
> aubdump: Support EXECBUFFER2_WR
I'm rather annoyed because this wasn't sent to the intel-gfx list
AFAICT, there
On Mon, 13 Mar 2017, Petri Latvala wrote:
> A new intel-gpu-tools quarterly release is available with the
> following changes:
> Jason Ekstrand (1):
> aubdump: Support EXECBUFFER2_WR
I'm rather annoyed because this wasn't sent to the intel-gfx list
AFAICT, there
Hans de Goede writes:
> For glx calls to work on libglvnd as glx provider we must first call
> glXGetClientString. This also means that we can no longer take the
> shortcut to not open the Display when a driver name is past to options.
This seems sensible. Hopefully
Adam Jackson writes:
> There's really no reason to pretend to support this, apps hate it, all
> we're doing is giving people a way to injure themselves. It doesn't work
> anyway with any Radeon, any NVIDIA chip, or any Intel chip since i810.
> Rip out all the logic for handling
Keith Packard writes:
> [ Unknown signature status ]
> Adam Jackson writes:
>
>> Is there some reason you believe GL's rasterisation rules for lines
>> match fb's zero-width lines? Section 14.5.1 of the 4.5 spec looks quite
>> a bit looser than fb to me.
>
> I
On Sat, Mar 11, 2017 at 12:26:38PM +0100, Gergely Nagy wrote:
> Largely based on work by Peter Hutterer, this patch makes composite relative +
> absolute devices work with the driver. Such devices are anything that presents
> itself as both a mouse, and - for example - a touch screen, like the
>
On 03/13/2017 11:32 AM, Nathan Schulte wrote:
> On 03/07/2017 05:56 PM, Jack Coulter wrote:
>> Is it possible for there to be multiple monitors for a single output, at
>> least as far as the RandR protocol is concerned, and is support simply
>> needed in xrandr, or is what I'm trying to do simply
On Wed, Mar 15, 2017 at 02:01:06PM +0100, walter harms wrote:
> you are aware the glibc does not support static linking ?
>
> re,
> wh
The glibc caveats surrounding static linking are completely orthogonal to
what is happening here. The library order in the link phase matters and
`pkg-config
On Wed, 2016-11-02 at 12:49 -0400, Adam Jackson wrote:
> This code is using GetImage to accumulate a logical view of the window
> image (since the windows will be clipped to their containing screen),
> and then PutImage to load that back into the pixmap. What it wasn't
> doing was constructing a
On Wed, 2017-03-15 at 15:55 -0400, Adam Jackson wrote:
> On Tue, 2017-03-14 at 14:58 +0100, Olivier Fourdan wrote:
>
> > There are some cases where we don't have a fallback code path, in which
> > case we'll avoid the crash in glamor_set_destination_drawable() but won't
> > render properly, but
On Tue, 2017-03-14 at 14:58 +0100, Olivier Fourdan wrote:
> There are some cases where we don't have a fallback code path, in which
> case we'll avoid the crash in glamor_set_destination_drawable() but won't
> render properly, but this is a rare occurence and not rendering properly
> is still
On Wed, 2017-03-15 at 10:23 +0900, Michel Dänzer wrote:
> On 14/03/17 11:22 PM, Olivier Fourdan wrote:
> > On startup, Xephyr does not check for the successful creation of its
> > screen pixmap, and would crash if it fails.
> >
> > The following patches aim at exiting cleanly instead of
Hi,
Read man xinput, see option map-to-output.
Then you can query the transformation matrix using xinput and
use the values in an xorg.conf piece, like these below so they are
applied as soon as the X server starts. This example works for
two X displays with identical resolutions side by side.
A couple more minor fixes, most notably a revert of a page-flipping
change that regressed some drivers.
Adam Jackson (2):
Revert "present: Allow flipping with PRIME slave outputs"
xserver 1.19.3
Chris Wilson (2):
Revert "prime: Sync shared pixmap from root window instead of
A couple more minor fixes, most notably a revert of a page-flipping
change that regressed some drivers.
Adam Jackson (2):
Revert "present: Allow flipping with PRIME slave outputs"
xserver 1.19.3
Chris Wilson (2):
Revert "prime: Sync shared pixmap from root window instead of
On Mon, 2017-03-13 at 06:06 -0400, Olivier Fourdan wrote:
> Hi,
>
> I have cherry-picked a couple of fixes for Xwayland for the
> server-1.19-branch.
>
> _Important_: I squashed two commits from upstream for 1.19, namely:
>
> 64ca14b xwayland: make sure client is not gone in sync callback
>
Hi,
I need to run multiple touch screens on an OpenSuSE 13.2 system, as well as on
an Ubuntu 16.04. Every thing works „fine“ when the system only has one graphics
card (Nvidia) installed. Unfortunately the systems is required to provide two
graphics cards. In this case the system has two
you are aware the glibc does not support static linking ?
re,
wh
Am 15.03.2017 02:16, schrieb x...@pengaru.com:
> Hello list,
>
> I'm trying to support clean-ish static linking of a small autotools and
> libx11-using monitoring program via:
>
> PKG_CONFIG="pkg-config --static"
On 03/06/2017 07:02 PM, Eric Anholt wrote:
> For re-adding an FBO cache, I would need to see that we have
> APPLE_object_purgeable used so that the FBO cache can be evicted, [...]
When I checked a few months ago, only the i915 Mesa and kernel drivers
implemented this. Maybe we can enable the FBO
On Wed, Mar 15, 2017 at 18:13:09 +0900, Michel Dänzer wrote:
> Same problem with fullscreen and windowed?
I can't really tell. The tearing happens in the upper part of the
screen. When moving the mpv window to the top of the screen, the
location where tearing happens in fullscreen mode is
On 15/03/17 05:53 PM, Tino Mettler wrote:
> On Wed, Mar 15, 2017 at 10:34:48 +0900, Michel Dänzer wrote:
>> On 14/03/17 07:52 PM, Tino Mettler wrote:
>>> Hi,
>>>
>>> I get tearing video with the modesetting driver on a Debian Sid
>>> installation.
>>
>> Which desktop environment are you using?
>
On Wed, Mar 15, 2017 at 10:34:48 +0900, Michel Dänzer wrote:
> On 14/03/17 07:52 PM, Tino Mettler wrote:
> > Hi,
> >
> > I get tearing video with the modesetting driver on a Debian Sid
> > installation.
>
> Which desktop environment are you using?
I use Gnome3 (as cited below).
>
>
> > It
28 matches
Mail list logo