On 01/10/2014 03:01 AM, Michel Dänzer wrote:
> On Fre, 2014-01-10 at 02:31 +0100, Roland Plüss wrote:
>> On 01/10/2014 02:09 AM, Michel Dänzer wrote:
>>> On Don, 2014-01-09 at 13:20 +0100, Roland Plüss wrote:
On 01/09/2014 04:01 AM, Michel Dänzer wrote:
>> How exactly could DRI2 make a pr
On Fre, 2014-01-10 at 02:31 +0100, Roland Plüss wrote:
> On 01/10/2014 02:09 AM, Michel Dänzer wrote:
> > On Don, 2014-01-09 at 13:20 +0100, Roland Plüss wrote:
> >> On 01/09/2014 04:01 AM, Michel Dänzer wrote:
> How exactly could DRI2 make a problem with the cat driver?
> >>> DRI2 is not the
On 01/10/2014 02:09 AM, Michel Dänzer wrote:
> On Don, 2014-01-09 at 13:20 +0100, Roland Plüss wrote:
>> On 01/09/2014 04:01 AM, Michel Dänzer wrote:
How exactly could DRI2 make a problem with the cat driver?
>>> DRI2 is not the problem, it's a possible solution. :) One of the main
>>> motiva
On 01/09/2014 02:01 AM, Thomas Lübking wrote:
> On Mittwoch, 8. Januar 2014 12:20:24 CEST, Roland Plüss wrote:
>
>> xwininfo: Window id: 0x561 (has no name)
>> Depth: 24
>> Visual: 0x23
>> Visual Class: TrueColor
>> Class: InputOutput
>> Colormap: 0x20 (installed)
>> Map State: IsV
On 01/09/2014 07:59 AM, Thomas Lübking wrote:
> On Donnerstag, 9. Januar 2014 02:29:59 CEST, Roland Plüss wrote:
>> It looks thus as if the GL rendering output area lags behind the window
>> position/size change as if the Compositor does apply the X event to the
>> X window but swallows the update
On 01/09/2014 04:01 AM, Michel Dänzer wrote:
> On Don, 2014-01-09 at 03:23 +0100, Roland Plüss wrote:
>> On 01/09/2014 02:31 AM, Michel Dänzer wrote:
>>> On Mit, 2014-01-08 at 11:50 +0100, Roland Plüss wrote:
On 01/08/2014 02:28 AM, Michel Dänzer wrote:
> On Mit, 2014-01-08 at 01:14 +0100
On Don, 2014-01-09 at 03:23 +0100, Roland Plüss wrote:
> On 01/09/2014 02:31 AM, Michel Dänzer wrote:
> > On Mit, 2014-01-08 at 11:50 +0100, Roland Plüss wrote:
> >> On 01/08/2014 02:28 AM, Michel Dänzer wrote:
> >>> On Mit, 2014-01-08 at 01:14 +0100, Roland Plüss wrote:
> Is reparenting with
On 01/09/2014 02:31 AM, Michel Dänzer wrote:
> On Mit, 2014-01-08 at 11:50 +0100, Roland Plüss wrote:
>> On 01/08/2014 02:28 AM, Michel Dänzer wrote:
>>> On Mit, 2014-01-08 at 01:14 +0100, Roland Plüss wrote:
Is reparenting with compositing a huge problem by itself?
>>> Seems to work just fin
On 01/09/2014 02:01 AM, Thomas Lübking wrote:
> On Mittwoch, 8. Januar 2014 12:20:24 CEST, Roland Plüss wrote:
>
>> xwininfo: Window id: 0x561 (has no name)
>> Depth: 24
>> Visual: 0x23
>> Visual Class: TrueColor
>> Class: InputOutput
>> Colormap: 0x20 (installed)
>> Map State: IsV
On Mit, 2014-01-08 at 11:50 +0100, Roland Plüss wrote:
> On 01/08/2014 02:28 AM, Michel Dänzer wrote:
> > On Mit, 2014-01-08 at 01:14 +0100, Roland Plüss wrote:
> >> Is reparenting with compositing a huge problem by itself?
> > Seems to work just fine for me. Which driver stack are you using? Maybe
On 01/08/2014 04:50 AM, Thomas Lübking wrote:
> On Mittwoch, 8. Januar 2014 01:14:20 CEST, Roland Plüss wrote:
>
>> You have a window with an OpenGL context for 3D rendering.
>> You create the window with XCreateWindow and an OpenGL infused visual
>> (glXChooseVisual).
>> After creating it you rep
On 01/08/2014 02:28 AM, Michel Dänzer wrote:
> On Mit, 2014-01-08 at 01:14 +0100, Roland Plüss wrote:
>> Is reparenting with compositing a huge problem by itself?
> Seems to work just fine for me. Which driver stack are you using? Maybe
> post your Xorg.0.log file and/or test app.
>
>
X.Org X Serv
12 matches
Mail list logo
