https://bugs.freedesktop.org/show_bug.cgi?id=92438
--- Comment #28 from Jim Blandy ---
(In reply to Jim Blandy from comment #26)
> Thanks for looking into this! I still get segfaults. The entry in
> extension_table for GL_ARB_direct_state_access is:
>
>{
https://bugs.freedesktop.org/show_bug.cgi?id=92438
--- Comment #26 from Jim Blandy ---
(In reply to Ilia Mirkin from comment #24)
> Hmmm... looks like rust isn't quite ready for prime-time -- there is no
> 'cargo' gentoo ebuild. (Apparently cargo can't be built hermetically?)
https://bugs.freedesktop.org/show_bug.cgi?id=92438
--- Comment #27 from Ilia Mirkin ---
Created attachment 119323
--> https://bugs.freedesktop.org/attachment.cgi?id=119323=edit
deal with bind == 0
Oh blast, you're right. Can't disable GL_ARB_direct_state_access, since
https://bugs.freedesktop.org/show_bug.cgi?id=92438
--- Comment #30 from Ilia Mirkin ---
(In reply to Jim Blandy from comment #29)
> (In reply to Ilia Mirkin from comment #27)
> > Created attachment 119323 [details]
> > deal with bind == 0
> >
> > Oh blast, you're right.
https://bugs.freedesktop.org/show_bug.cgi?id=90626
--- Comment #17 from Ilia Mirkin ---
Could one of you post an acpidump from the laptop? Specifically interested in
how the _ROM method is defined.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=92438
--- Comment #29 from Jim Blandy ---
(In reply to Ilia Mirkin from comment #27)
> Created attachment 119323 [details]
> deal with bind == 0
>
> Oh blast, you're right. Can't disable GL_ARB_direct_state_access, since it's
>
https://bugs.freedesktop.org/show_bug.cgi?id=90351
--- Comment #1 from Erik van Pienbroek
---
This bug still exists on kernel 4.3.0-rc7.
The patch mentioned here still behaves the same as mentioned in the initial bug
report (backlight of internal
An interesting results.
DRI2:
$ vblank_mode=0 glxgears
ATTENTION: default value of option vblank_mode overridden by environment.
6321 frames in 5.0 seconds = 1264.103 FPS
6380 frames in 5.0 seconds = 1275.943 FPS
6369 frames in 5.0 seconds = 1273.629 FPS
6377 frames in 5.0 seconds = 1275.322
https://bugs.freedesktop.org/show_bug.cgi?id=91972
--- Comment #5 from Austin English ---
(In reply to Ilia Mirkin from comment #1)
> Wow, very uncommon configuration... nouveau as main and intel as "GPU". Are
> you doing any actual offloading (of either outputs or
On 31.10.2015 06:55, Daniel Vetter wrote:
> Apparently pre-nv50 pageflip events happen before the actual vblank
> period. Therefore that functionality got semi-disabled in
>
> commit af4870e406126b7ac0ae7c7ce5751f25ebe60f28
> Author: Mario Kleiner
> Date: Tue May 13
10 matches
Mail list logo