search for: nv98

For NV98+, BSP/VP/PPP are all FUC-based engines. Hook them all up in the same way as NVC0, but with a couple of different values. Also make sure that the PPP engine is handled in the fifo/mc/vm. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- It seems like VP4.0 is basically working here......

https://bugs.freedesktop.org/show_bug.cgi?id=104845 Bug ID: 104845 Summary: Nouveau NV98 : 0 A.D. game creates memory mess after short time 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=77586 Priority: medium Bug ID: 77586 Assignee: nouveau at lists.freedesktop.org Summary: [NV98] On recent Linux kernel (3.13 and 3.14), the GPU locks up around the time an X server starts QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified OS: Linux (All) Reporter: jkloos at mpi-sws.org...

https://bugs.freedesktop.org/show_bug.cgi?id=86164 Bug ID: 86164 Summary: Dual screen causes KDE crash on NV50 (NV98) in nouveau (bisected) Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee: nouveau...

...39;s also a hypothetical concern of "what if we create an open >> firmware with a different user API". Ideally there'd be some way to >> expose what kind of firmware is loaded, but I think that can be left >> for "later". > I also happened to notice that NV98, NVA1+ refer to these nv84 engines > (in drivers/gpu/drm/nouveau/core/engine/device/nv50.c). I assume that > means I should create a new nv98.c version of BSP/VP that resembles > the old versions of nv84.c, and point device/nv50.c at those for nv98 > and nva1+? nv98+ should really have...

https://bugs.freedesktop.org/show_bug.cgi?id=90390 Bug ID: 90390 Summary: [NV98] Modesetting causes blank screen because of INVALID_STATE [UNK0B] chid 1 mthd 0x0080 data 0x00000000 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW...

...t.edu> --- v1 -> v2: - factored out similar logic between vp and bsp into a new xtensa.c, similar to falcon - moved firmware loading to init rather than ctor (kinda wonder what happens if you suspend while playing a video... hmm.) - created new "blank" copies of vp/bsp for nv98+, identical to the old nv84 ones, but s/84/98/g At this point I have H.264 and MPEG1/2 working fairly well. Back when there were bugs in my mesa code, VP would freeze up sometimes and the watchdog would fire. I have no idea how to actually reset the engine though... so it's just a notificat...

http://bugs.freedesktop.org/show_bug.cgi?id=27136 Summary: blank screen with G98 [Quadro NVS 420] (NV98) dual GPU, 4-head Product: xorg Version: 7.5 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at l...

4.1.8-200.fc22.x86_64 dmesg: [ 11.809467] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x098200a2 [ 11.809493] nouveau [ DEVICE][0000:02:00.0] Chipset: G98 (NV98) [ 11.809508] nouveau [ DEVICE][0000:02:00.0] Family : NV50 4.3.0-0.rc4.git0.1.fc24.x86_64 dmesg: [ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2) Where vanished these Chipset & Family super cool lines?

$ 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 "gpu0" Driver "nouveau" EndSection $ ps -C glmark2 -o cmd,pcpu CMD %CPU glmark...

On 02.12.2014 14:40, Ilia Mirkin wrote: > On Tue, Dec 2, 2014 at 8:38 AM, poma <pomidorabelisima at gmail.com> wrote: >> Is this expected result for Chipset: G98 (NV98)? > > Yep, 100% expected. [Perhaps you might glance at the wiki page you got > that from for clues as to why.] > "You basically never need to do the mmiotrace, unless you're a nouveau developer."? I did everything by the book[1]. Though I don't need this, I still...

...concern of "what if we create an open >>> firmware with a different user API". Ideally there'd be some way to >>> expose what kind of firmware is loaded, but I think that can be left >>> for "later". >> >> I also happened to notice that NV98, NVA1+ refer to these nv84 engines >> (in drivers/gpu/drm/nouveau/core/engine/device/nv50.c). I assume that >> means I should create a new nv98.c version of BSP/VP that resembles >> the old versions of nv84.c, and point device/nv50.c at those for nv98 >> and nva1+? >>...

These chipsets include the VP2 engine which is composed of a bitstream processor (BSP) that decodes H.264 and a video processor (VP) which can do iDCT/mo-comp/etc for MPEG1/2, H.264, and VC-1. Both of these are driven by separate xtensa chips embedded in the hardware. This patch provides the mechanism to load the kernel for the xtensa chips and provide the necessary interactions to do the rest of

Is this expected result for Chipset: G98 (NV98)? $ modinfo nvidia -F version 304.123 $ stat -c %s mmiotrace.log 134659197 $ file mmiotrace.log mmiotrace.log: ASCII text $ grep -i lost mmiotrace.log ; echo $? 1 $ ./envytools/rnn/demmio -f mmiotrace.log | perl -e 'open($fh409c, ">fuc409c"); open($fh409d, ">fuc409d&qu...

On 15.09.2014 15:36, Ilia Mirkin wrote: > On Mon, Sep 15, 2014 at 4:23 AM, poma <pomidorabelisima at gmail.com> wrote: >> Chipset: G98 (NV98) >> Family : NV50 >> >> >> WORKING VIDEO RESUME(S3) >> >> 3.15.0-rc8.1.git.7a014a8 >> 3.15.0-rc8.2.git.456b057 >> 3.15.0-rc8.3.git.b8407c9 >> 3.15.0-rc8.4.git.bb7ef1e >> >> ======================== >> >> BROKEN VIDEO RESU...

https://bugs.freedesktop.org/show_bug.cgi?id=96737 Bug ID: 96737 Summary: G98: LightDM 1 : 0 Nouveau Product: xorg Version: git Hardware: All OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org

...ubdev/clock/nvc0.o +nouveau-$(CONFIG_DRM_NOUVEAU_NVC0) += core/subdev/clock/nve0.o nouveau-y += core/subdev/clock/pllnv04.o nouveau-y += core/subdev/clock/pllnva3.o nouveau-y += core/subdev/devinit/base.o @@ -76,7 +76,7 @@ nouveau-y += core/subdev/devinit/nv84.o nouveau-y += core/subdev/devinit/nv98.o nouveau-y += core/subdev/devinit/nva3.o nouveau-y += core/subdev/devinit/nvaf.o -nouveau-y += core/subdev/devinit/nvc0.o +nouveau-$(CONFIG_DRM_NOUVEAU_NVC0) += core/subdev/devinit/nvc0.o nouveau-y += core/subdev/fb/base.o nouveau-y += core/subdev/fb/nv04.o nouveau-y += core/subdev/fb/nv10.o...

Pan Bříza, to se stane, když Custom image - Pick a file from your drives(s) ... nouveau 0000:02:00.0: fifo: DMA_PUSHER - ch 5 [mediawriter[20975]] get 0020171c34 put 00201746ec ib_get 00000017 ib_put 00000018 state 8000a32c (err: INVALID_CMD) push 00406040 nouveau 0000:02:00.0: gr: DATA_ERROR 00000004 [INVALID_VALUE] nouveau 0000:02:00.0: gr: 00100000 [] ch 5 [001f7bd000 mediawriter[20975]] subc 5

Hello poma, The chipset didn't disappear and is still displayed: it is the G98 you get on the "[ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2)" line. The "NV98" was the "Nouveau" chipset, but the switch was made to use the same naming as NVIDIA. So rather than displaying both the Nouveau version of the chipset and the NVIDIA one, it make sense to only use one, and to prefer the NVIDIA naming. (FYI, files name has been modified to follow the...

...bdev/devinit/nv04.o -nouveau-y += core/subdev/devinit/nv05.o -nouveau-y += core/subdev/devinit/nv10.o -nouveau-y += core/subdev/devinit/nv1a.o -nouveau-y += core/subdev/devinit/nv20.o -nouveau-y += core/subdev/devinit/nv50.o -nouveau-y += core/subdev/devinit/nv84.o -nouveau-y += core/subdev/devinit/nv98.o -nouveau-y += core/subdev/devinit/nva3.o -nouveau-y += core/subdev/devinit/nvaf.o -nouveau-y += core/subdev/devinit/nvc0.o +nouveau-$(CONFIG_DRM_NOUVEAU_NV04) += core/subdev/devinit/nv04.o +nouveau-$(CONFIG_DRM_NOUVEAU_NV04) += core/subdev/devinit/nv05.o +nouveau-$(CONFIG_DRM_NOUVEAU_NV04) += cor...