From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 40931] r600g: interpret integer texture types as ints regresses VDPAU/XVMC decode.
Date: Fri, 16 Sep 2011 11:16:14 -0700 (PDT) [thread overview]
Message-ID: <20110916181614.C509A1300B2@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-40931-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=40931
--- Comment #5 from Marek Olšák <maraeo@gmail.com> 2011-09-16 11:16:13 PDT ---
(In reply to comment #4)
> Hi Dave & Andy,
>
> I think we have a disagreement here about what SCALED types should be.
>
> As I understood it SCALED types should be represented as integers in memory,
> but when loaded into a shader converted to floats in the range 0..2^n (in
> opposite to normalized types), and that's how I used them in g3dvl.
That's right if you are talking about USCALED.
--
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
next prev parent reply other threads:[~2011-09-16 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 10:17 [Bug 40931] New: r600g: interpret integer texture types as ints regresses VDPAU/XVMC decode bugzilla-daemon
2011-09-16 13:21 ` [Bug 40931] " bugzilla-daemon
2011-09-16 14:42 ` bugzilla-daemon
2011-09-16 16:45 ` bugzilla-daemon
2011-09-16 16:52 ` bugzilla-daemon
2011-09-16 18:16 ` bugzilla-daemon [this message]
2011-09-16 18:27 ` bugzilla-daemon
2011-09-24 12:53 ` bugzilla-daemon
2011-09-26 10:18 ` bugzilla-daemon
2012-11-02 14:31 ` 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=20110916181614.C509A1300B2@annarchy.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;
as well as URLs for NNTP newsgroup(s).