From: Programmeur fou <programmeur.fou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stephane Marchesin
<stephane.marchesin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau <Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: Gart to vram/vram to gart transfers broken on NVS 140M
Date: Fri, 23 Apr 2010 08:24:21 +0200 [thread overview]
Message-ID: <4BD13D15.8080205@gmail.com> (raw)
In-Reply-To: <x2g6a89f9d51004220320w47174461l295eac76baa1e0e1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Le 22/04/2010 12:20, Stephane Marchesin a écrit :
> On Thu, Apr 22, 2010 at 03:13, Martin Peres<martin.peres-GANU6spQydw@public.gmane.org> wrote:
>
>> Hi Nouveau folks,
>>
>> I've been encountering some corruption on pixmaps for a while now, and it
>> seems like the problem comes from the DFS/UTS (Download From Screen / Upload
>> To Screen).
>>
>> In fact, I'm pretty sure the problem comes from there as screenshots are
>> garbled and so does a few more things.
>>
>> I may have time to dig this up, where should I start, is there some
>> documentation on the NVS 140M ? Where is the gart2vram code located ?
>> Do you have any idea of where could be the problem ?
>>
>>
> If you really think that's UTS/DFS, edit nouveau_exa.c and disable
> them (change the UTS/DFS functions to return FALSE, that'll trigger
> fallbacks to sw copying).
>
> Stephane
OK, I'll try this out tonight. I'll keep you in touch.
next prev parent reply other threads:[~2010-04-23 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 10:13 Gart to vram/vram to gart transfers broken on NVS 140M Martin Peres
[not found] ` <4BD02139.4090506-GANU6spQydw@public.gmane.org>
2010-04-22 10:20 ` Stephane Marchesin
[not found] ` <x2g6a89f9d51004220320w47174461l295eac76baa1e0e1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-23 6:24 ` Programmeur fou [this message]
2010-04-25 16:45 ` Martin PERES
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=4BD13D15.8080205@gmail.com \
--to=programmeur.fou-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=stephane.marchesin-Re5JQEeQqe8AvxtiuMwx3w@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.