On 25 January 2017 at 02:26, Michel Dänzer wrote:
> On 24/01/17 11:32 PM, Adam Jackson wrote:
>> On Tue, 2017-01-24 at 10:40 +1000, Peter Hutterer wrote:
>>> Heads up: I'll be pushing the following three patches into all xorg
>>> repositories that need it in the next few days.
On 24/01/17 11:32 PM, Adam Jackson wrote:
> On Tue, 2017-01-24 at 10:40 +1000, Peter Hutterer wrote:
>> Heads up: I'll be pushing the following three patches into all xorg
>> repositories that need it in the next few days. Speak up now or be
>> forever silent, etc. etc.
>
> Convention so far has
On 23 January 2017 at 19:32, Adam Jackson wrote:
> I'd like to move the module loader up to dix. In preparation for that, here's
> a bunch of cleanup patches. The first three aren't mine, I just think they're
> neat.
>
s/three/four/ and thank you.
I'll try to re-spin my
On 23 January 2017 at 19:32, Adam Jackson wrote:
> The idea here is that the driver might have once been old enough to not
> have the driverFunc slot in DriverRec, with the module ABI not having
> changed when it was added. That was ages ago, and drivers always declare
>
On 23 January 2017 at 19:32, Adam Jackson wrote:
> Nobody who is using this functionality is ever not specifying a major
> version, which makes sense. If you don't care about a minor version,
> that's equivalent to saying you require minor >= 0, so just say so;
> likewise patch
Olivier Fourdan writes:
> When selecting "CA_TWO_PASS" in glamor_composite_clipped_region() when
> the hardware does not support "GL_ARB_blend_func_extended", we call
> glamor_composite_choose_shader() twice in a row, which in turn calls
> glamor_pixmap_ensure_fbo().
>
> On
Adam Jackson writes:
> Should you find yourself using a 16bpp display while also using a
> compositor, you poor soul, you may find that your GLX applications
> behave strangely; in particular, glxgears will be transparent. This is
> because it clears to (0,0,0,0) which is
When selecting "CA_TWO_PASS" in glamor_composite_clipped_region() when
the hardware does not support "GL_ARB_blend_func_extended", we call
glamor_composite_choose_shader() twice in a row, which in turn calls
glamor_pixmap_ensure_fbo().
On memory pixmaps, the first call will set the FBO and the
> There is a fundamental logical problem with this patch though, because
> glamor_upload_picture_to_texture() does:
>
> assert(glamor_pixmap_is_memory(pixmap));
>
> which is basically priv->type == GLAMOR_MEMORY;
>
> So glamor_upload_picture_to_texture() clearly expects a pixmap of type
>
On Mon, 2017-01-23 at 19:00 +0100, Tobias Stoeckmann wrote:
> On Mon, Jan 23, 2017 at 11:52:13AM -0500, Adam Jackson wrote:
> > Not that any caller has likely made this mistake, but you want an
> > if
> > (number) before this, otherwise you turn a protocol error into a
> > segfault.
>
> If a
On Tue, 2017-01-24 at 10:40 +1000, Peter Hutterer wrote:
> Heads up: I'll be pushing the following three patches into all xorg
> repositories that need it in the next few days. Speak up now or be
> forever silent, etc. etc.
Convention so far has been to strip xf86-{video,input}- from the driver
Am 24.01.2017 09:18, schrieb Julien Cristau:
> On Tue, Jan 24, 2017 at 01:12:23 +, James Clarke wrote:
>
>> Hi,
>> I've been debugging an issue in gtk2-perl causing it to SIGBUS on
>> sparc64, and traced it back to what seems to be dodgy code inside
>> libx11. One of the tests calls
Hi
> If the pixmap type is neither GLAMOR_TEXTURE_ONLY nor GLAMOR_TEXTURE_DRM
> we might have the fbo field set but the gl_fbo still set to the default
> GLAMOR_FBO_UNATTACHED, which later may fail an assert in
> glamor_upload_picture_to_texture().
>
> Bugzilla:
On Tue, Jan 24, 2017 at 01:12:23 +, James Clarke wrote:
> Hi,
> I've been debugging an issue in gtk2-perl causing it to SIGBUS on
> sparc64, and traced it back to what seems to be dodgy code inside
> libx11. One of the tests calls gdk_window_set_opacity, which calls
> XChangeProperty with a
14 matches
Mail list logo