dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 25871] nearest neighbour samples wrong texel (precision/rounding problem)
Date: Tue, 11 Sep 2012 11:32:01 +0000	[thread overview]
Message-ID: <bug-25871-502-Y1CKSf3Wyi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-25871-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=25871

Andreas Boll <andreas.boll.dev@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Drivers/DRI/R600            |Drivers/Gallium/r600

--- Comment #5 from Andreas Boll <andreas.boll.dev@gmail.com> 2012-09-11 11:32:01 UTC ---
(In reply to comment #4)
> Created attachment 43951 [details] [review]
> possible fix
> 
> Does this patch help?

this patch has been committed as

commit 1dc204d145dc8c0b19473a7814c201a8954b6274
Author: Alex Deucher <alexdeucher@gmail.com>
Date:   Mon Feb 28 21:52:19 2011 -0500

    r600g: truncate point sampled texture coordinates

    By default the hardware rounds texcoords.  However,
    for point sampled textures, the expected behavior is
    to truncate.  When we have point sampled textures,
    set the truncate bit in the sampler.

    Should fix:
    https://bugs.freedesktop.org/show_bug.cgi?id=25871

    Signed-off-by: Alex Deucher <alexdeucher@gmail.com>

and reverted in

commit 72c6a748b9ffdaa893f82faf911f22a241a5e4f5
Author: Marek Olšák <maraeo@gmail.com>
Date:   Mon May 2 01:10:19 2011 +0200

    Revert "r600g: truncate point sampled texture coordinates"

    This reverts commit 1dc204d145dc8c0b19473a7814c201a8954b6274.

    MC_COORD_TRUNCATE is for MPEG and produces quite an interesting behavior
    on regular textures. Anyway that commit broke filtering in demos/cubemap.


reassigning to r600g

is this still an issue with a newer mesa (e.g. 8.0.4 or git master)?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2012-09-11 11:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-03 13:01 [Bug 25871] New: nearest neighbour samples wrong texel (precision/rounding problem) bugzilla-daemon
2010-01-04 21:48 ` [Bug 25871] " bugzilla-daemon
2010-01-04 21:49 ` bugzilla-daemon
2011-03-01  2:27 ` bugzilla-daemon
2011-03-01  2:56 ` bugzilla-daemon
2012-09-11 11:32 ` bugzilla-daemon [this message]
2012-09-11 13:51 ` bugzilla-daemon
2012-09-11 17:12 ` bugzilla-daemon
2012-09-11 17:23 ` bugzilla-daemon
2012-09-12 12:34 ` bugzilla-daemon
2012-09-12 13:03 ` bugzilla-daemon
2012-09-12 13:56 ` bugzilla-daemon
2014-04-13 10:46 ` bugzilla-daemon
2014-04-13 20:40 ` bugzilla-daemon
2014-04-13 22:39 ` bugzilla-daemon
2014-04-16  8:13 ` bugzilla-daemon
2014-04-16 15:15 ` bugzilla-daemon

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=bug-25871-502-Y1CKSf3Wyi@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox