All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres-GANU6spQydw@public.gmane.org>
To: Maarten Maathuis <madman2003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: rendering problems with latest ddx driver (nv50)
Date: Tue, 24 Apr 2012 20:51:30 +0200	[thread overview]
Message-ID: <4F96F632.1090608@free.fr> (raw)
In-Reply-To: <CAGZ4FERhLZdXm51i4wbDxNNjU1g3SP6uX6399eKtR7LRWO_PQw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1152 bytes --]

Le 24/04/2012 20:49, Maarten Maathuis a écrit :
> On Tue, Apr 24, 2012 at 8:36 PM, Martin Peres<martin.peres-GANU6spQydw@public.gmane.org>  wrote:
>> Le 24/04/2012 20:14, Maarten Maathuis a écrit :
>>
>>> Do you get rendering errors also when using a nv50 class gpu? I seem
>>> to get them in firefox.
>>>
>>> I also noticed a huge amount of failures when running rendercheck -t
>>> gradients, which i find odd, because they are not supposed to be
>>> accelerated.
>> Hi,
>>
>> By any chance, are you using cairo 1.12? If so, try downgrading to cairo
>> 1.10.
>>
>> Martin
> No, i'm using cairo 1.10.2. Also rendercheck isn't affected by cairo.
> The last driver upgrade included at least the migration to the new
> libdrm and everything that came after it. That's when the rendering
> corruption started.
>
Right, I was under the asumption that both issues were un-related.

I guess you are using the latest ddx which does accelerate solid pictures.
Have you tried resetting to this commit ? 
http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=ec019b3a50475b7ff1b5e0a5dbe14e5ef677bd9e

Please keep us posted

[-- Attachment #1.2: Type: text/html, Size: 2021 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2012-04-24 18:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 18:14 rendering problems with latest ddx driver (nv50) Maarten Maathuis
     [not found] ` <CAGZ4FETeOjfQD5DV1+=sx4NCk9xuMrvQhH1fS-TrmoVRiMc7mQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-24 18:36   ` Martin Peres
     [not found]     ` <4F96F2C8.900-GANU6spQydw@public.gmane.org>
2012-04-24 18:49       ` Maarten Maathuis
     [not found]         ` <CAGZ4FERhLZdXm51i4wbDxNNjU1g3SP6uX6399eKtR7LRWO_PQw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-24 18:51           ` Martin Peres [this message]
2012-04-25  0:38   ` Ben Skeggs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F96F632.1090608@free.fr \
    --to=martin.peres-ganu6spqydw@public.gmane.org \
    --cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=madman2003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.