search for: gf117

GF117 appears to use the same register as GK104 (but still with the general Fermi readout mechanism). Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108980 Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- v1 -> v2: split out different regid into separate file. .../drm/nouveau...

...ned-off-by: Samuel Pitoiset <samuel.pitoiset at gmail.com> --- drm/nouveau/include/nvkm/subdev/ibus.h | 1 + drm/nouveau/nvkm/engine/device/base.c | 4 +-- drm/nouveau/nvkm/subdev/ibus/Kbuild | 1 + drm/nouveau/nvkm/subdev/ibus/gf100.c | 17 ++++++++++-- drm/nouveau/nvkm/subdev/ibus/gf117.c | 51 ++++++++++++++++++++++++++++++++++ drm/nouveau/nvkm/subdev/ibus/priv.h | 7 +++++ 6 files changed, 77 insertions(+), 4 deletions(-) create mode 100644 drm/nouveau/nvkm/subdev/ibus/gf117.c create mode 100644 drm/nouveau/nvkm/subdev/ibus/priv.h diff --git a/drm/nouveau/include/nvkm/s...

https://bugs.freedesktop.org/show_bug.cgi?id=104393 Bug ID: 104393 Summary: GF117 volting not possible Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org...

https://bugs.freedesktop.org/show_bug.cgi?id=108980 Bug ID: 108980 Summary: GF117: MMIO write of 0000001f FAULT at 6013d4 [ IBUS ] Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Ass...

NVIDIA provided the documentation for mp error 0x10, INVALID_ADDR_SPACE, which apparently happens when trying to use an atomic operation on local or shared memory (instead of global memory). Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drm/nouveau/nvkm/engine/gr/gf100.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drm/nouveau/nvkm/engine/gr/gf100.c

We get 1 warning when biuld kernel with W=1: drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf117.c:222:1: warning: no previous prototype for 'gf117_grctx_generate_main' [-Wmissing-prototypes] In fact, this function is only used in the file in which it is declared and don't need a declaration, but can be made static. so this patch marks this function with 'static'. Signed-...

We get 1 warning when build kernel with W=1: drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf117.c:222:1: warning: no previous prototype for 'gf117_grctx_generate_main' [-Wmissing-prototypes] In fact, this function is only used in the file in which it is declared and don't need a declaration, but can be made static. so this patch marks this function with 'static'. Signed-...

This commit should be backported to kernel 4.3 (apologies for line-wrapping). Without it, we get a null deref (i.e. oops) on GF117 GPUs which for one reason or another don't have the PMU hooked up. That should be fixed in its own right, but that's a separate matter. The issue was introduced in commit e2ca4e7d6e (drm/nouveau/pmu: convert to new-style nvkm_subdev) commit 579b7c58215329803ce184704463de09f0f310ac Author:...

...an/nouveau.man | 9 ++++++++- src/nv_driver.c | 8 ++++++-- 2 files changed, 14 insertions(+), 3 deletions(-) diff --git a/man/nouveau.man b/man/nouveau.man index 07d53c8..4878f24 100644 --- a/man/nouveau.man +++ b/man/nouveau.man @@ -63,7 +63,14 @@ GF100, GF104, GF106, GF108, GF110, GF114, GF116, GF117, GF119 GK104, GK106, GK107, GK110, GK208 .TP 22 .B GeForce GTX 750 -GM107 +GM107, GM108 +.TP 22 +.B GeForce GTX 9XX +GM200, GM204, GM206 +.TP 22 +.B GeForce GTX 10XX +GP102, GP104, GP106, GP107, GP108 + .SH CONFIGURATION DETAILS Please refer to __xconfigfile__(__filemansuffix__) for general...

https://bugs.freedesktop.org/show_bug.cgi?id=92870 Bug ID: 92870 Summary: GF117M nvkm_pmu_pgob fault Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.free...

...ng LZO decompression as > part of performing the copy. It has a variety of limitations (e.g., > cannot handle blocklinear format), and was only in a few Fermi chips, > as I understand it. According to our driver source, GF100, GF104, GF110, GF114, and GF116 all have it. [So GF106, GF108, GF117, GF119 don't have it.] We've only had problems reported against GF116... and only for some people. > > It is probably easiest to just ignore it. You can distinguish this > decompress engine from normal copy engine by looking at the CE capability > register on falcon (0x0000065...

On Tue, Nov 06, 2018 at 06:41:22PM +0200, Ville Syrjälä wrote: > On Tue, Nov 06, 2018 at 05:24:15PM +0100, Thierry Reding wrote: > > From: Thierry Reding <treding at nvidia.com> > > > > Irrespective of whether or not the device has any usable outputs, the > > modesetting helpers will try to register all the resources such as CRTCs > > and planes.

...ing the copy. It has a variety of limitations (e.g., >> > cannot handle blocklinear format), and was only in a few Fermi chips, >> > as I understand it. >> >> According to our driver source, GF100, GF104, GF110, GF114, and GF116 >> all have it. [So GF106, GF108, GF117, GF119 don't have it.] We've only >> had problems reported against GF116... and only for some people. > > Hmm, some of our internal documentation is inconsistent about whether it > applies to GF100, but otherwise what I see matches your list. I guess > "few" was...

...a display engine, in which > case we'd need the DRIVER_MODESET feature again, but I'm not aware of > anyone doing that, so it may not be worth planning for that at this > point. I thought DRIVER_MODESET was required even for rendernodes. Is that no longer the case? Note that e.g. GF117 GPUs also don't have a display engine hooked up in nouveau (or in hardware). -ilia

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108980 Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drivers/gpu/drm/nouveau/nvkm/engine/falcon.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/falcon.c b/drivers/gpu/drm/nouveau/nvkm/engine/falcon.c index 816ccaedfc73..8675613e142b 100644 ---

...51, MCP61 .TP 22 .B GeForce 7XXX -G70, G71, G72, G73 +G70, G71, G72, G73, MCP67, MCP68, MCP73 +.TP 22 +.B GeForce 8XXX, 9XXX, 2XX, 3XX +G80, G84, G86, G92, G94, G96, G98, G200, GT215, GT216, GT218, MCP77, +MCP79, MCP89 +.TP 22 +.B GeForce 4XX, 5XX +GF100, GF104, GF106, GF108, GF110, GF114, GF116, GF117, GF119 +.TP 22 +.B GeForce 6XX, 7XX +GK104, GK106, GK107, GK110, GK208 +.TP 22 +.B GeForce GTX 750 +GM107 .SH CONFIGURATION DETAILS Please refer to __xconfigfile__(__filemansuffix__) for general configuration @@ -67,6 +80,10 @@ are supported: .BI "Option \*qHWCursor\*q \*q" boolean \...

...hing can be done for better support for that hardware > > The errors are just some unexpected things in the vbios. I think > 3.16-rc1+ should know about that voltage table? Maybe not. Either way, > it's important for reclocking, and we don't have support for that for > nvd7 (gf117). > > Are you having any issues, or just reporting funny things in your dmesg? > > -ilia > I have some artifacts during login, see: http://s27.postimg.org/iqvwytuir/2014_07_10_200731_1366x768_scrot.png http://s27.postimg.org/d2u7lofk3/2014_07_10_200737_1366x768_scrot.png after...

...he Optimus architecture, handle by PRIME. The bug is currently with the kernel 5.2.0, but it have always been like that as far as I remember. uname -a : Linux ga-laptop 5.2.0-arch2-1-ARCH #1 SMP PREEMPT Mon Jul 8 18:18:54 UTC 2019 x86_64 GNU/Linux lspci : 01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1) While it is not in use, nouveau shutdown the chipset as expected : cat /sys/kernel/debug/dri/1/pstate 07: core 270 MHz memory 405 MHz 0f: core 625 MHz memory 900 MHz DC: core 0 MHz memory 0 MHz While an app is launched with DRI_PRIM...

Hello in dmesg I always have these informations (I tested several kernels between 3.7 and 3.16-rc3): [ 13.742006] nouveau E[ DRM] Pointer to TMDS table invalid [ 13.742036] nouveau [ DRM] DCB version 4.0 [ 13.742038] nouveau E[ DRM] Pointer to flat panel table invalid [ 13.742079] nouveau [ DRM] ACPI backlight interface available, not registering our own [ 13.742082]

...gt; part of performing the copy. It has a variety of limitations (e.g., > > cannot handle blocklinear format), and was only in a few Fermi chips, > > as I understand it. > > According to our driver source, GF100, GF104, GF110, GF114, and GF116 > all have it. [So GF106, GF108, GF117, GF119 don't have it.] We've only > had problems reported against GF116... and only for some people. Hmm, some of our internal documentation is inconsistent about whether it applies to GF100, but otherwise what I see matches your list. I guess "few" was not entirely accurate....