[Nouveau] [Bug 90626] HP ZBook 15 nouveau driver hangup for kernel >= 4.1

https://bugs.freedesktop.org/show_bug.cgi?id=90626 --- Comment #35 from Ortwin Glück --- (In reply to Ilia Mirkin from comment #34) > Hmmm... did you see a "hw bug workaround enabled" line? Are you using Linux > 4.3? [4.2 and older didn't have the workaround logic.] Ok works fine

[Nouveau] [PATCH] pci: enable c800 magic for Clevo P157SM

this is needed for my gpu --- drm/nouveau/nvkm/engine/device/pci.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/engine/device/pci.c b/drm/nouveau/nvkm/engine/device/pci.c index e3c783d..d506e02 100644 --- a/drm/nouveau/nvkm/engine/device/pci.c +++

[Nouveau] [PATCH 1/2] disp: activate dual link TMDS links only when possible

From: Hauke Mehrtens Without this patch a pixel clock rate above 165 MHz on a TMDS link is assumed to be dual link. This is true for DVI, but not for HDMI. HDMI supports no dual link, but it supports pixel clock rates above 165 MHz. Only activate Dual Link mode when it is

[Nouveau] [PATCH 2/2] connector: allow 225/297MHz pixel clocks for HDMI on Fermi/Kepler

Some Fermi's apparently alow allow 297MHz clocks, so create a parameter which allows end-users to set it themselves until we have a reliable way to determine the board's maximum pixel clocks. Signed-off-by: Ilia Mirkin --- drm/nouveau/nouveau_connector.c | 15

Re: [Nouveau] [PATCH 1/2] disp: activate dual link TMDS links only when possible

On Tue, Nov 3, 2015 at 7:02 PM, Ben Skeggs wrote: > On 11/04/2015 08:41 AM, Ilia Mirkin wrote: >> From: Hauke Mehrtens >> >> Without this patch a pixel clock rate above 165 MHz on a TMDS link is >> assumed to be dual link. This is true for DVI, but not for

[Nouveau] [Bug 70354] [NVE6, NVE7] HUB_INIT timeout on graph init, blob fw doesn't help

https://bugs.freedesktop.org/show_bug.cgi?id=70354 --- Comment #87 from Ilia Mirkin --- (In reply to Julien Isorce from comment #86) > I only tested with patch+workaround, but maybe "patch" is enough. I can try > to confirm tomorrow. Thx! Please do -- the workaround is

[Nouveau] Nouveau for FreeBSD

Any progress on the FreeBSD front? ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau

[Nouveau] [Bug 70354] [NVE6, NVE7] HUB_INIT timeout on graph init, blob fw doesn't help

https://bugs.freedesktop.org/show_bug.cgi?id=70354 --- Comment #84 from Julien Isorce --- I think I now why the workaround is no applied, it is because it is only for NVE4, 6 and 7. And my GT 750M seems to be threatened as "NVC0 (GF100) GeForce GTX (465, 470, 480,

[Nouveau] [Bug 70354] [NVE6, NVE7] HUB_INIT timeout on graph init, blob fw doesn't help

https://bugs.freedesktop.org/show_bug.cgi?id=70354 --- Comment #86 from Julien Isorce --- (In reply to Ilia Mirkin from comment #85) > (In reply to Julien Isorce from comment #84) > > Any idea ? Thx > > You have a GK107. It probably needs the PGOB fix as well as another

Re: [Nouveau] [PATCH 1/2] disp: activate dual link TMDS links only when possible

On 11/04/2015 10:37 AM, Ilia Mirkin wrote: > On Tue, Nov 3, 2015 at 7:02 PM, Ben Skeggs wrote: >> On 11/04/2015 08:41 AM, Ilia Mirkin wrote: >>> From: Hauke Mehrtens >>> >>> Without this patch a pixel clock rate above 165 MHz on a TMDS link is >>> assumed to

[Nouveau] [Bug 91236] [NVC3] Passive DP to HDMI adapter cannot use pixel clocks greater than 165 MHz

https://bugs.freedesktop.org/show_bug.cgi?id=91236 --- Comment #5 from Ilia Mirkin --- With the below pair of patches, you should be able to set any max pixel clock you like. http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=8d5fe3328855063bb41acb00b1049138acce8e2e

[Nouveau] [PATCH] kms: no need to check for empty edid before drm_detect_hdmi_monitor

Signed-off-by: Ilia Mirkin --- drm/nouveau/nv50_display.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drm/nouveau/nv50_display.c b/drm/nouveau/nv50_display.c index bdaba91..d9cba87 100644 --- a/drm/nouveau/nv50_display.c +++ b/drm/nouveau/nv50_display.c @@ -773,7

[Nouveau] [Bug 70354] [NVE6, NVE7] HUB_INIT timeout on graph init, blob fw doesn't help

https://bugs.freedesktop.org/show_bug.cgi?id=70354 --- Comment #85 from Ilia Mirkin --- (In reply to Julien Isorce from comment #84) > Any idea ? Thx You have a GK107. It probably needs the PGOB fix as well as another user on this bug needed it. See

[Nouveau] [PATCH v2 1/2] disp: activate dual link TMDS links only when possible

From: Hauke Mehrtens Without this patch a pixel clock rate above 165 MHz on a TMDS link is assumed to be dual link. This is true for DVI, but not for HDMI. HDMI supports no dual link, but it supports pixel clock rates above 165 MHz. Only activate Dual Link mode when it is

[Nouveau] [PATCH v2 2/2] connector: allow 225/297MHz pixel clocks for HDMI on Fermi/Kepler

Some Fermi's apparently alow allow 297MHz clocks, so create a parameter which allows end-users to set it themselves until we have a reliable way to determine the board's maximum pixel clocks. Signed-off-by: Ilia Mirkin --- drm/nouveau/nouveau_connector.c | 25

Re: [Nouveau] [PATCH 1/2] disp: activate dual link TMDS links only when possible

On 11/04/2015 08:41 AM, Ilia Mirkin wrote: > From: Hauke Mehrtens > > Without this patch a pixel clock rate above 165 MHz on a TMDS link is > assumed to be dual link. This is true for DVI, but not for HDMI. HDMI > supports no dual link, but it supports pixel clock rates above

[Nouveau] [PATCH v3 2/2] connector: allow 225/297MHz pixel clocks for HDMI on Fermi/Kepler

Some Fermi's apparently alow allow 297MHz clocks, so create a parameter which allows end-users to set it themselves until we have a reliable way to determine the board's maximum pixel clocks. Signed-off-by: Ilia Mirkin --- drm/nouveau/nouveau_connector.c | 24

[Nouveau] [PATCH v3 1/2] disp: activate dual link TMDS links only when possible

From: Hauke Mehrtens Without this patch a pixel clock rate above 165 MHz on a TMDS link is assumed to be dual link. This is true for DVI, but not for HDMI. HDMI supports no dual link, but it supports pixel clock rates above 165 MHz. Only activate Dual Link mode when it is

[Nouveau] [Bug 91236] [NVC3] Passive DP to HDMI adapter cannot use pixel clocks greater than 165 MHz

https://bugs.freedesktop.org/show_bug.cgi?id=91236 --- Comment #6 from Andrew Boettcher --- I am reporting the patches worked great! Indeed I am now viewing this bug with a screen in 297 MHz over a passive DP to HDMI connector. Before we missed the second part where the

Re: [Nouveau] Nouveau for FreeBSD

Is anyone actually and or actively working on this? Github.com/pathscale/pscnv is totally bitrot but waaay more portable base. Nouveau made hard Linux assumptions that will be difficult to overcome afaik.

Re: [Nouveau] Nouveau for FreeBSD

Nouveau kernel module has a largely os-agnostic "core" component (called nvkm/nvif now) which encompasses the actual operation of the GPU. The drm wrapper around it provides the relevant interfaces for KMS/ioctls/etc. Any port would want the ioctl bits as well, since that's what the userspace

[Nouveau] [Bug 73373] [NVE4] GPU lockup after opening many tabs in Chromium web browser

https://bugs.freedesktop.org/show_bug.cgi?id=73373 --- Comment #19 from Mario Barrera --- (In reply to Ilia Mirkin from comment #18) > (In reply to Mario Barrera from comment #15) > > Maybe useful, opening about 10 tabs with embedded flash elements in Firefox > > seems to cause

[Nouveau] [Bug 73373] [NVE4] GPU lockup after opening many tabs in Chromium web browser

https://bugs.freedesktop.org/show_bug.cgi?id=73373 --- Comment #21 from Mario Barrera --- Created attachment 119387 --> https://bugs.freedesktop.org/attachment.cgi?id=119387=edit opening several HTML files with Firefox -- You are receiving this mail because: You are the

[Nouveau] [Bug 73373] [NVE4] GPU lockup after opening many tabs in Chromium web browser

https://bugs.freedesktop.org/show_bug.cgi?id=73373 --- Comment #20 from Mario Barrera --- Created attachment 119386 --> https://bugs.freedesktop.org/attachment.cgi?id=119386=edit opening several HTML files with Firefox -- You are receiving this mail because: You are the