search for: nv108

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

https://bugs.freedesktop.org/show_bug.cgi?id=101273 Bug ID: 101273 Summary: [NV108] Random kernel panic 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...

From: Martin Peres <martin.peres at labri.fr> --- nvkm/subdev/pwr/fuc/kernel.fuc | 13 +++++++++++++ nvkm/subdev/pwr/fuc/nv108.fuc.h | 25 +++++++++++-------------- nvkm/subdev/pwr/fuc/nva3.fuc.h | 23 ++++++++++------------- nvkm/subdev/pwr/fuc/nvc0.fuc.h | 23 ++++++++++------------- nvkm/subdev/pwr/fuc/nvd0.fuc.h | 23 ++++++++++------------- 5 files changed, 54 insertions(+), 53 deletions(-) diff --git a/nvkm/subde...

Re-use the therm-exported fan structure with only two minor modifications: - pwm_freq: u16 -> u32; - add fan_type (toggle or PWM) v2: - Do not memset the table to 0 as it erases the pre-set default values Signed-off-by: Martin Peres <martin.peres at free.fr> --- drm/Kbuild | 1 + drm/core/include/subdev/bios/fan.h | 1 + drm/core/subdev/bios/fan.c | 1

...mxm/base.o nouveau-y += core/subdev/mxm/mxms.o nouveau-y += core/subdev/mxm/nv50.o nouveau-y += core/subdev/pwr/base.o nouveau-y += core/subdev/pwr/memx.o nouveau-y += core/subdev/pwr/nva3.o -nouveau-y += core/subdev/pwr/nvc0.o -nouveau-y += core/subdev/pwr/nvd0.o -nouveau-y += core/subdev/pwr/nv108.o +nouveau-$(CONFIG_DRM_NOUVEAU_NVC0) += core/subdev/pwr/nvc0.o +nouveau-$(CONFIG_DRM_NOUVEAU_NVC0) += core/subdev/pwr/nvd0.o +nouveau-$(CONFIG_DRM_NOUVEAU_NVC0) += core/subdev/pwr/nv108.o nouveau-y += core/subdev/therm/base.o nouveau-y += core/subdev/therm/fan.o nouveau-y += core/subdev/therm/f...

https://bugs.freedesktop.org/show_bug.cgi?id=71472 Priority: medium Bug ID: 71472 Assignee: nouveau at lists.freedesktop.org Summary: GT-740M not detected QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: temnota.am at gmail.com Hardware:

...v/mxm/mxms.o > nouveau-y += core/subdev/mxm/nv50.o > nouveau-y += core/subdev/pwr/base.o > nouveau-y += core/subdev/pwr/memx.o > nouveau-y += core/subdev/pwr/nva3.o > -nouveau-y += core/subdev/pwr/nvc0.o > -nouveau-y += core/subdev/pwr/nvd0.o > -nouveau-y += core/subdev/pwr/nv108.o > +nouveau-$(CONFIG_DRM_NOUVEAU_NVC0) += core/subdev/pwr/nvc0.o > +nouveau-$(CONFIG_DRM_NOUVEAU_NVC0) += core/subdev/pwr/nvd0.o > +nouveau-$(CONFIG_DRM_NOUVEAU_NVC0) += core/subdev/pwr/nv108.o > nouveau-y += core/subdev/therm/base.o > nouveau-y += core/subdev/therm/fan.o > no...

https://bugs.freedesktop.org/show_bug.cgi?id=91354 Bug ID: 91354 Summary: [Quadro K610M] "xset dpms force on" blinks the screen Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=74710 Priority: medium Bug ID: 74710 Assignee: nouveau at lists.freedesktop.org Summary: GT 730M: unknown chipset QA Contact: xorg-team at lists.x.org Severity: blocker Classification: Unclassified OS: Linux (All) Reporter: mail at tobias-neumann.eu

Actually GM108 is not one of the recognized chips. Someone needs to go through and check that its goldens didn't change. Nobody's done that. See https://bugs.freedesktop.org/show_bug.cgi?id=89558 On Thu, Mar 31, 2016 at 4:57 PM, Pierre Moreau <pierre.morrow at free.fr> wrote: > Hello, > > Acceleration support for GM107 was merged in kernel 4.1, and modesetting > support

...DIA Corporation GK208 HDMI/DP Audio Controller (rev a1) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) RAM is 4G text part of glxinfo: --------------------- Extended renderer info (GLX_MESA_query_renderer): Vendor: nouveau (0x10de) Device: NV108 (0x1282) Version: 12.0.1 Accelerated: yes Video memory: 1013MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: no...

On 01-12-15, Samuel Pitoiset wrote: >>> Ok, here is a MMT trace of vectorAdd: >>> >>> https://fedorapeople.org/~jwrdegoede/vectorAdd.log.gz >> >> Hi Hans, >> >> Thanks a lot. > > Well, I didn't know but Martin has a GK208... > I just tested the compute support on his card and ... it works without > any changes. :-)

...vers/gpu/drm/nouveau/Makefile > @@ -236,6 +236,7 @@ nouveau-y += core/engine/fifo/nv50.o > nouveau-y += core/engine/fifo/nv84.o > nouveau-y += core/engine/fifo/nvc0.o > nouveau-y += core/engine/fifo/nve0.o > +nouveau-y += core/engine/fifo/nvea.o > nouveau-y += core/engine/fifo/nv108.o > nouveau-y += core/engine/graph/ctxnv40.o > nouveau-y += core/engine/graph/ctxnv50.o > diff --git a/drivers/gpu/drm/nouveau/core/engine/fifo/nve0.h b/drivers/gpu/drm/nouveau/core/engine/fifo/nve0.h > index 014344e..e96b32b 100644 > --- a/drivers/gpu/drm/nouveau/core/engine/fifo/...

...descriptions e9fb980 drm/nve0/fifo: document more intr status bits 9f8459c drm/nve0/fifo: populate PBDMA status bitfield with more definitions 39b0554 drm/nve0/fifo: s/subfifo/PBDMA/ f82c44a drm/nve0/fifo: s/playlist/runlist/ f76dd80 drm/nvf0/gr: enable acceleration with our chsw ucode aa97cd3 drm/nv108/gr: enable acceleration with our chsw ucode 5d91e19 drm/nvc0-/gr: handle fwmthd interrupts in ucode e1b22bc drm/nvc0-/gr: fiddle some magic around strand init 96616b4 drm/nv108/gr: initial support (need external fuc) daa9ab5 drm/nv108/ce: enable copy engines a763951 drm/nv108/fifo: initial support...

There might be some callers of nouveau_clock_astate(), and they are from inetrrupt context. So we must ensure that this function can be atomic in that condition. This patch adds one parameter which is subsequently passed to nouveau_pstate_calc(). Therefore we can choose whether we want to wait for the pstate work's completion or not. Signed-off-by: Vince Hsu <vinceh at nvidia.com> ---

...core/subdev/mxm/nv50.o +nouveau-$(CONFIG_DRM_NOUVEAU_NVC0) += core/subdev/mxm/nv50.o nouveau-y += core/subdev/pwr/base.o nouveau-y += core/subdev/pwr/memx.o -nouveau-y += core/subdev/pwr/nva3.o -nouveau-y += core/subdev/pwr/nvc0.o -nouveau-y += core/subdev/pwr/nvd0.o -nouveau-y += core/subdev/pwr/nv108.o +nouveau-$(CONFIG_DRM_NOUVEAU_NV50) += core/subdev/pwr/nva3.o +nouveau-$(CONFIG_DRM_NOUVEAU_NVC0) += core/subdev/pwr/nvc0.o +nouveau-$(CONFIG_DRM_NOUVEAU_NVC0) += core/subdev/pwr/nvd0.o +nouveau-$(CONFIG_DRM_NOUVEAU_NVC0) += core/subdev/pwr/nv108.o nouveau-y += core/subdev/therm/base.o nouveau-...

Oh, hum, GM108 is NV118 and not NV108 which is Gk208… My bad! SMF from the bug report seemed to have some working setup, and since he didn't pinged back, I guess it's working nicely. But some more checking might still be needed? On 04:59 PM - Mar 31 2016, Ilia Mirkin wrote: > Actually GM108 is not one of the recognized chi...

...commit/3da1f2a19e5e8dc8d68a4400d9cca01c64ecd59e). I guess it will make it into 4.7. Pierre On 12:14 PM - Apr 18 2016, Sune Mølgaard wrote: > Is there anything I can do in this regard? > > /smo > > On 2016-03-31 23:12, Pierre Moreau wrote: > > Oh, hum, GM108 is NV118 and not NV108 which is Gk208… My bad! > > > > SMF from the bug report seemed to have some working setup, and since he didn't > > pinged back, I guess it's working nicely. But some more checking might still be > > needed? > > > > On 04:59 PM - Mar 31 2016, Ilia Mirkin...

...used the wrong card on reator (which is the REing machine of Martin). The primary card is a GK106 and the second one is the GK208. That doesn't explain why I did something wrong but heh? :-) You are right. With those bits added locally, the compute support totally hangs the GPU on my GK208 (NV108), and a reboot is needed. Please give a shot at this branch : http://cgit.freedesktop.org/~hakzsam/mesa/log/?h=nvf0_compute It fixes the initialization of the compute state and allows me to launch 'test_input_global' (ie. ./compute 8) on my GK208 without any dmesg fails. That's a good...

Hi, I used to experience kernel panics caused by CPUx hard lockup once almost everyday. I'm running Ubuntu 14.10 on vanilla linux kernel 3.19.2 on Core i7-3770 with Gallium 0.4 on NV108. The panic log looked like: [ 9227.509744] ------------[ cut here ]------------ [ 9227.509750] WARNING: CPU: 0 PID: 0 at kernel/watchdog.c:290 watchdog_overflow_callback+0x92/0xc0() [ 9227.509751] Watchdog detected hard LOCKUP on cpu 0 [ 9227.509751] Modules linked in: rfcomm bnep bluetooth intel_...