Re: [Nouveau] [Mesa-dev] [PATCH] nvc0: fix geometry program revalidation of clipping params

2015-07-13 Thread Samuel Pitoiset
What piglit test does this fix? On Sat, Jul 11, 2015 at 7:13 PM, Ilia Mirkin wrote: > Signed-off-by: Ilia Mirkin > Cc: mesa-sta...@lists.freedesktop.org > --- > > Even though in practice a geometry program will never be using UCP's, > we still were revalidating (aka recompiling) the program whe

[Nouveau] [Bug 91319] Nouveau driver cannot extract FCODE ROM / DCB Block from OpenFirmware Device tree

2015-07-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91319 Peter Saisanas changed: What|Removed |Added CC||psaisa...@gmail.com --- Comment #1 from

[Nouveau] [Bug 91319] Nouveau driver cannot extract FCODE ROM / DCB Block from OpenFirmware Device tree

2015-07-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91319 --- Comment #2 from Ilia Mirkin --- Aha, looks like the issue is that your VBIOS in OF does not have a PCIR section, and the nouveau VBIOS parser has come to expect that. Going to have to read more code to work out a proper solution to that. --

Re: [Nouveau] [Mesa-dev] [PATCH] nvc0: fix geometry program revalidation of clipping params

2015-07-13 Thread Ilia Mirkin
Any one which, after using a geometry shader, enables an extra clip distance. i.e. none. On Mon, Jul 13, 2015 at 4:16 AM, Samuel Pitoiset wrote: > What piglit test does this fix? > > On Sat, Jul 11, 2015 at 7:13 PM, Ilia Mirkin wrote: >> >> Signed-off-by: Ilia Mirkin >> Cc: mesa-sta...@lists.fr

Re: [Nouveau] [Mesa-dev] [PATCH] nvc0: fix geometry program revalidation of clipping params

2015-07-13 Thread Ilia Mirkin
This was, btw, introduced in commit 3a8ae6ac243b (nvc0: adapt to new clip state). Back then there was no real geometry support yet. On Mon, Jul 13, 2015 at 2:05 PM, Ilia Mirkin wrote: > Any one which, after using a geometry shader, enables an extra clip > distance. i.e. none. > > On Mon, Jul 13,

Re: [Nouveau] CUDA fixed VA allocations and sparse mappings

2015-07-13 Thread Andrew Chew
I apologize for my ignorance. In digging through nouveau, I've become a bit confused regarding the relationship between virtual address allocations and nouveau bo's. From my reading of the code, it seems that a nouveau_bo really encapsulates a buffer (whether imported, or allocated within nouveau

[Nouveau] [Bug 90513] Odd gray and red flicker in The Talos Principle on GK104

2015-07-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=90513 --- Comment #9 from Karol Herbst --- yeah I can confirm this. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ Nouveau mailing list Nou

[Nouveau] [Bug 91333] New: Connecting second of two monitors to a Lenovo W520 causes displays to go crazy

2015-07-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91333 Bug ID: 91333 Summary: Connecting second of two monitors to a Lenovo W520 causes displays to go crazy Product: xorg Version: unspecified Hardware: Other OS:

[Nouveau] [Bug 91333] Connecting second of two monitors to a Lenovo W520 causes displays to go crazy

2015-07-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91333 --- Comment #1 from Corey Ashford --- xorg-x11-drv-nouveau-1.0.11-2.fc22.x86_64 is what I have installed -- You are receiving this mail because: You are the assignee for the bug. ___ Nouveau mailing

[Nouveau] [Bug 91333] Connecting second of two monitors to a Lenovo W520 causes displays to go crazy

2015-07-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91333 --- Comment #2 from Ilia Mirkin --- While "going crazy" is rarely the right thing to do, I'd like to point out that a GF108 only has 2 CRTC's and thus can only ever power 2 different screens at a time. (There might be a way to drive 2 identical s

[Nouveau] [Bug 91333] Connecting second of two monitors to a Lenovo W520 causes displays to go crazy

2015-07-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91333 --- Comment #3 from Corey Ashford --- (In reply to Ilia Mirkin from comment #2) > While "going crazy" is rarely the right thing to do, I'd like to point out > that a GF108 only has 2 CRTC's and thus can only ever power 2 different > screens at a

[Nouveau] [Bug 91333] Connecting second of two monitors to a Lenovo W520 causes displays to go crazy

2015-07-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91333 --- Comment #4 from Ilia Mirkin --- I bet it works if you first disable one of the screens before plugging a third one in. -- You are receiving this mail because: You are the assignee for the bug. ___

Re: [Nouveau] [PATCH] Add Option "DRI3" to allow to disable DRI3 under EXA.

2015-07-13 Thread Mario Kleiner
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 d

[Nouveau] [Bug 91333] Connecting second of two monitors to a Lenovo W520 causes displays to go crazy

2015-07-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91333 --- Comment #5 from Corey Ashford --- (In reply to Ilia Mirkin from comment #4) > I bet it works if you first disable one of the screens before plugging a > third one in. I had tried that experiment before, but I just now tried it again. Same b

[Nouveau] [Bug 91333] Connecting second of two monitors to a Lenovo W520 causes displays to go crazy

2015-07-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91333 --- Comment #6 from Corey Ashford --- Created attachment 117105 --> https://bugs.freedesktop.org/attachment.cgi?id=117105&action=edit Similar as first log, but this time I disable the laptop's display before adding the second monitor -- You a

[Nouveau] [Bug 91333] Connecting second of two monitors to a Lenovo W520 causes displays to go crazy

2015-07-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=91333 --- Comment #7 from Corey Ashford --- In both of these log files is a line like the following: 48.693955] nouveau E[ PDISP][:01:00.0] INVALID_STATE [UNK05] chid 0 mthd 0x0080 data 0x Followed by a dump of what appears to be inter