similar to: "enable dri3 support without glamor" causes gnome-shell regression on nv4x

Displaying 20 results from an estimated 2000 matches similar to: ""enable dri3 support without glamor" causes gnome-shell regression on nv4x"

2015 Aug 03
3
"enable dri3 support without glamor" causes gnome-shell regression on nv4x
Hi, On 30-07-15 16:09, Ilia Mirkin wrote: > FWIW this is a fail on nv50+ as well. See for example > https://bugs.freedesktop.org/show_bug.cgi?id=91445 > > My suspicion is that this is due to the lack of PUSH_KICK in the *Done > exa handlers -- works fine with DRI2, but DRI3 has no synchronization > and so the commands never get flushed out. Easily verified by sticking >
2015 Aug 03
2
"enable dri3 support without glamor" causes gnome-shell regression on nv4x
Hi, On 03-08-15 17:36, Ilia Mirkin wrote: > On Mon, Aug 3, 2015 at 9:02 AM, Hans de Goede <hdegoede at redhat.com> wrote: >> Hi, >> >> On 30-07-15 16:09, Ilia Mirkin wrote: >>> >>> FWIW this is a fail on nv50+ as well. See for example >>> https://bugs.freedesktop.org/show_bug.cgi?id=91445 >>> >>> My suspicion is that this is
2015 Aug 10
2
"enable dri3 support without glamor" causes gnome-shell regression on nv4x
Hi, On 03-08-15 20:09, Ilia Mirkin wrote: > On Mon, Aug 3, 2015 at 1:31 PM, Hans de Goede <hdegoede at redhat.com> wrote: >> Hi, >> >> >> On 03-08-15 17:36, Ilia Mirkin wrote: >>> >>> On Mon, Aug 3, 2015 at 9:02 AM, Hans de Goede <hdegoede at redhat.com> wrote: >>>> >>>> Hi, >>>> >>>> On
2015 Jul 14
3
[PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.
On 07/07/2015 09:51 PM, Ilia Mirkin wrote: > Lastly, from some discussions with ajax on IRC, it appears that DRI3 > is half-baked at best wrt sync between server and client. I think we > should just disable it by default for now, until issues are ironed > out. (Rather than what this patch has, which is default-on for Xorg > > some version.) What are the remaining known trouble
2015 Jun 30
3
[PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.
X-Server versions older than 1.16.3 have bugs in their DRI3/Present implementation which impair nouveau, so it is better to stick to good old DRI2 by default on such servers. E.g., page flipping doesn't work at all under DRI3/Present with older servers, and use of extensions like OML_sync_control, SGI_video_sync or INTEL_swap_events also causes failure of Present. nouveau's glamor accel
2015 Jul 04
2
[PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.
That would be great, as long as it does only that and does not go into the "drivername" territory. As the said driver ;-) "A driver name to use can be provided instead of simple boolean value, which will be passed to the GL implementation for it to load the appropriate backend." -Emil On 4 July 2015 at 18:17, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > IMO
2015 Jul 04
2
[PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.
The DRI option with the intel ddx can be used to indicate the following - whether dri is disabled - the dri "version" - dri1, dri2, dri3 - the dri module name - doo_dri.so bar_dri.so I'm not sure how exactly it's supposed to work/works, and I believe most of that is due to legacy reasons. I'm just saying let's not do the whole thing - just the dri "version"
2015 Jul 14
4
[PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.
On 07/14/2015 05:26 PM, Ilia Mirkin wrote: > On Mon, Jul 13, 2015 at 11:43 PM, Mario Kleiner > <mario.kleiner.de at gmail.com> wrote: >> On 07/07/2015 09:51 PM, Ilia Mirkin wrote: >>> >>> Lastly, from some discussions with ajax on IRC, it appears that DRI3 >>> is half-baked at best wrt sync between server and client. I think we >>> should just
2015 Jul 27
4
[PATCH] nouveau: nv46: Change mc subdev oclass from nv44 to nv4c
Hi, On 24-07-15 04:32, Ben Skeggs wrote: > On 24 July 2015 at 01:20, Hans de Goede <hdegoede at redhat.com> wrote: >> MSI interrupts appear to not work for nv46 based cards. Change the mc >> subdev oclass for these cards from nv44 to nv4c, the nv4c mc code is >> identical to the nv44 mc code except that it does not use msi >> (it does not define a msi_rearm
2015 Jul 19
2
[PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.
On 07/18/2015 01:09 PM, Dave Airlie wrote: >>>> >>>> We can disable it by default on exa - intel and amd/radeon drivers also >>>> disable by default. However, on gpus >= maxwell only glamor accel is >>>> supported and glamor on nouveau is either dri3/present or no hw accel at >>>> all >>>> afaics. >>> >>>
2015 Jul 29
3
[PATCH 1/2] present: Fixup return type of nouveau_present_init()
Make it a Bool consistently, as declared in header. Reported-by: Ilia Mirkin <imirkin at alum.mit.edu> Signed-off-by: Mario Kleiner <mario.kleiner.de at gmail.com> --- src/nouveau_present.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/nouveau_present.c b/src/nouveau_present.c index 4de1e6e..699a58d 100644 --- a/src/nouveau_present.c +++
2015 Nov 02
2
NOUVEAU(0): DRI3 on EXA enabled
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 FPS 6387 frames in 5.0 seconds = 1277.330 FPS 6407 frames in 5.0 seconds = 1281.337 FPS 6381 frames in
2015 Nov 04
3
NOUVEAU(0): DRI3 on EXA enabled
On 04.11.2015 11:57, Martin Peres wrote: > On 02/11/15 08:28, poma wrote: >> 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 =
2020 Aug 13
2
Accumulating CPU load from Xorg process with DRI3
I observed this bug for quite some time, but so far I workarounded it with just setting DRI2 (default) in xorg.conf.d/20-nouveau.conf Now with two GPU i iwsh to use DRI3, so right now it set up like this: cat /etc/X11/xorg.conf.d/20-nouveau.conf Section "Device" Identifier "Card0" Driver "nouveau" Option "PageFlip" "1" #Option
2015 Jul 07
3
RFC: drop glamor from nouveau ddx
Ben, Looks like the reality is that glamor is just not hooked up properly in the nouveau DDX. Mainly it's missing DRI2, which in turn means no core GL contexts, and probably lots of other issues. While this could probably be fixed somehow, I doubt there's any advantage to using the nouveau DDX over something like modesetting nowadays. How would you feel about dropping glamor support from
2015 Jul 07
2
RFC: drop glamor from nouveau ddx
On Tue, Jul 7, 2015 at 5:05 PM, Ben Skeggs <skeggsb at gmail.com> wrote: > On 8 July 2015 at 06:06, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> Ben, >> >> Looks like the reality is that glamor is just not hooked up properly >> in the nouveau DDX. Mainly it's missing DRI2, which in turn means no >> core GL contexts, and probably lots of other
2016 Apr 07
2
glmark2: high CPU usage - DRI3 & modeset
$ glmark2 ======================================================= glmark2 2014.03 ======================================================= OpenGL Information GL_VENDOR: nouveau GL_RENDERER: Gallium 0.4 on NV98 GL_VERSION: 3.0 Mesa 11.2.0 ======================================================= /etc/X11/xorg.conf.d/nouveau.conf Section "Device" Identifier
2015 Dec 10
2
[ANNOUNCE] xf86-video-nouveau 1.0.12
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 New nouveau DDX release. Ben Skeggs (1): Bump version to 1.0.12 Ilia Mirkin (14): copy: don't bother trying to create copy on pre-nva3 allow path to envyas binary to be specified kepler: remove unnecessary texbars, add live-only tex for nvf0 use defined method names where available nv50: explicitly disable
2015 Dec 10
2
[ANNOUNCE] xf86-video-nouveau 1.0.12
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 New nouveau DDX release. Ben Skeggs (1): Bump version to 1.0.12 Ilia Mirkin (14): copy: don't bother trying to create copy on pre-nva3 allow path to envyas binary to be specified kepler: remove unnecessary texbars, add live-only tex for nvf0 use defined method names where available nv50: explicitly disable
2015 Jul 23
4
[PATCH] nouveau: nv46: Change mc subdev oclass from nv44 to nv4c
MSI interrupts appear to not work for nv46 based cards. Change the mc subdev oclass for these cards from nv44 to nv4c, the nv4c mc code is identical to the nv44 mc code except that it does not use msi (it does not define a msi_rearm callback). BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=90435 Signed-off-by: Hans de Goede <hdegoede at redhat.com> ---