From: Roland Scheidegger <sroland@vmware.com>
To: Xavier Chantry <chantry.xavier@gmail.com>
Cc: "mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>,
nouveau <nouveau@lists.freedesktop.org>
Subject: Re: RFC: gallium-msaa branch merge
Date: Sat, 22 May 2010 13:29:04 +0200 [thread overview]
Message-ID: <4BF7C000.6090001@vmware.com> (raw)
In-Reply-To: <AANLkTilG7aGderzZS5KtfLPFBvKDUrFCRrdq89cNAY4m@mail.gmail.com>
On 21.05.2010 23:40, Xavier Chantry wrote:
> Ok, after looking at how some other drivers were updated, I thought
> nouveau needed bigger changes than that.
> Jakob just pushed a simple build fix, and now nv50 builds and runs (almost ;)).
>
> I just noticed 5 piglit regressions :
> fbo/fbo-copypix
> fbo/fbo-copyteximage
> general/scissor-copypixels
> texturing/depth-level-clamp
> texturing/texredefine
>
>
> And I am not sure how important is the TODO mentioned in the commit log below.
>
> commit b59b23a51dc17da59ccff0b3f8a73009056746e5
> Author: Roland Scheidegger <sroland@vmware.com>
> Date: Mon May 17 21:28:14 2010 +0200
>
> nouveau: adapt to interface changes
>
> this probably needs further cleanup (just getting a surface for the resource
> seems quite nonoptimal and potentially cause unnecessary copies I think)
> _______________________________________________
> mesa-dev mailing list
> mesa-dev@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/mesa-dev
There was some logic in nouveau which decided when to update "shadow"
surfaces (which looked a bit odd at places). That used blit flags, and
since they are gone this might not really do what it used to do. I think
if it were changed to no longer use surfaces internally for copying this
would become much more obvious what to do.
Roland
prev parent reply other threads:[~2010-05-22 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BF2C897.8090008@vmware.com>
2010-05-21 19:41 ` RFC: gallium-msaa branch merge Xavier Chantry
[not found] ` <AANLkTilp8IaazHhOaTMTjeGc8kVnaKhKZXM60pyNrn1l-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-21 21:40 ` [Mesa-dev] " Xavier Chantry
2010-05-22 11:29 ` Roland Scheidegger [this message]
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=4BF7C000.6090001@vmware.com \
--to=sroland@vmware.com \
--cc=chantry.xavier@gmail.com \
--cc=mesa-dev@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.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.