similar to: [Bug 25275] New: [NV30] Graphical artefacts on PPC64

Hello developers, I recently participated in a public listening test that was held by German magazine c't. They had two categories, 64 kbps and 128 kbps. I only participated in the 64 kbps test where there were 7 .wav files, with 1 of them the original one and the other 6 being encoded with different encoders. Without knowing which file was encoded with which encoder you had to give each

https://bugs.freedesktop.org/show_bug.cgi?id=30286 Summary: Rendering Artefacts for "EffectFrames" with KWin trunk Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at

http://bugs.freedesktop.org/show_bug.cgi?id=26057 Summary: Artefacts in kde 4 Product: xorg Version: 7.4 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: alex.vizor at gmail.com

For all these patches I'd say: testers are welcome. The first three patches seem good enough to push as we speak IMHO (so if you agree, go ahead!), whereas for the fourth I don't know if this is the desired way to fix. The result of these four patches is that NV34 gives a nearly-correct desktop experience, where only some fading animations appear broken. It's quite useable now! [1/4]:

https://bugs.freedesktop.org/show_bug.cgi?id=91247 Bug ID: 91247 Summary: Tomb Raider: Underworld renders lots of artefacts on models and objects Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

On Mon, Sep 7, 2015 at 3:50 PM, Hans de Goede <hdegoede at redhat.com> wrote: > msaa use on nv30 may trigger a (mesa?) bug where dmesg says: > [ 1197.850642] nouveau E[soffice.bin[3785]] fail ttm_validate > [ 1197.850648] nouveau E[soffice.bin[3785]] validating bo list > [ 1197.850654] nouveau E[soffice.bin[3785]] validate: -12 > [ 1201.766955] nouveau E[soffice.bin[3785]]

A reworked version of 3 out of 4 patches mentioned earlier. [1/4]: Fixes nearly all piglit vertprog testcases, due to now being able to pass the results on to the fragment shader. V2: rename samplers to texcoords. [2/4]: Fixes shader compiler assertion errors, as some source registers do not exist for certain operations. Fixes several piglit tests when mesa is compiled with --enable-debug [3/4]:

http://bugs.freedesktop.org/show_bug.cgi?id=17571 Summary: Nouveau and PPC64 issues Product: xorg Version: unspecified Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

Dear all, I encoded and decoded some files using speex codec and I find out with than when using the original raw file and coding it in NB with different bit rate, complexity or with/without enhancement some kind of slight artefact (a strange low level sound appears) is created at t=1.12 s. This is just before an attack which is present in the signal. I did not try to solve the problems but if

I am trying to figure out why the ttm_bo_vm_fault is stitching pages from the GART instead of the pages allocated via DRM_NOUVEAU_GEM_NEW. And also why OUR_RINGp is writing 16, 256 and 512 bytes of zero filled data *1 in the GART? Perhaps I should mention that I know _why_ it is taking the pages from the GART and giving them to the userland - but I don't know if that is correct way of doing

Hi, I'm bitten by a bug that is also in the Debian BTS, so I'm not sure you are aware of it. I couldn't find it in the fdo BTS. Anyway the problem is simple. After a successful suspend and resume all window decorations (the places where the shadow was supposed to be, but also the titlebars) are much to colorful (meaning it has some random colors in it). Moving the windows brings the

https://bugs.freedesktop.org/show_bug.cgi?id=105173 Nick Lee <nvlbox at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact| |xorg-team at lists.x.org Component|General |Driver/nouveau Version|XOrg git

Hello, everybody I run the following program, and depending on the size of eps I get different results. With eps=1e-05, the program calculates wrong values for x=65:67 and others. The program runs fine with eps=1e-07. Why is this so? Also, I am using area() instead of integrate() because I cannot make integrate to work, especially with imaginary numbers. Maybe someone can show me how to use

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: "10.2" <mesa-stable at lists.freedesktop.org> --- src/gallium/drivers/nouveau/nv30/nv30_screen.c | 6 ++++++ src/gallium/drivers/nouveau/nv30/nvfx_fragprog.c | 1 + 2 files changed, 7 insertions(+) diff --git a/src/gallium/drivers/nouveau/nv30/nv30_screen.c b/src/gallium/drivers/nouveau/nv30/nv30_screen.c index

The sifm object has a limit of 1024x1024 for its input size and 2048x2048 for its output. The code checking this was trying to be clever resulting in it seeing a surface of e.g 1024x256 being outside of the input size limit. This commit fixes this. Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- src/gallium/drivers/nouveau/nv30/nv30_transfer.c | 4 ++-- 1 file changed, 2

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/gallium/drivers/nouveau/nv30/nv30_screen.c | 33 +++++++++++++------------- 1 file changed, 17 insertions(+), 16 deletions(-) diff --git a/src/gallium/drivers/nouveau/nv30/nv30_screen.c b/src/gallium/drivers/nouveau/nv30/nv30_screen.c index 4baabaf..5c3d783 100644 --- a/src/gallium/drivers/nouveau/nv30/nv30_screen.c +++

It should be possible to make this be 16 on nvc0. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Not touching nv50 since I have a patch that actually impelents support for multiple viewports there. src/gallium/drivers/nouveau/nv30/nv30_screen.c | 2 ++ src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 2 ++ 2 files changed, 4 insertions(+) diff --git

On 05/24/2015 06:58 AM, Ilia Mirkin wrote: > nv30_validate_clip depends on the rasterizer state. Also we should > upload all the new clip planes on change since next time the plane data > won't have changed, but the enables might. > > Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> > --- > src/gallium/drivers/nouveau/nv30/nv30_state_validate.c | 16

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Untested. Happened to see this when I was reading this file (don't ask). I can't imagine the current situation to be the intended one, based on this code... src/gallium/drivers/nouveau/nv30/nv30_state_validate.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

nvfx_fragprog_assign_generic only allows for up to 10/8 texcoords for nv40/nv30. This fixes compilation of the varying-packing tests (although they still fail). Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: 9.1 9.2 10.0 <mesa-stable at lists.freedesktop.org> --- src/gallium/drivers/nouveau/nv30/nv30_screen.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git