All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 40931] New: r600g: interpret integer texture types as ints regresses VDPAU/XVMC decode.
Date: Fri, 16 Sep 2011 03:17:25 -0700 (PDT)	[thread overview]
Message-ID: <bug-40931-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: r600g: interpret integer texture types as ints
                    regresses VDPAU/XVMC decode.
           Product: Mesa
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: lists@andyfurniss.entadsl.com


Using rv790 grey is rendered with VDPAU/XVMC decode since

commit f2bae9456f141f8c1104ef2a0aab31f6190ae5f0
Author: Dave Airlie <airlied@redhat.com>
Date:   Thu Sep 15 12:41:00 2011 +0100

    r600g: interpret integer texture types as ints.

    For signed/unsigned with no normalisation or srgb, assume its an INT
    type texture.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-09-16 10:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 10:17 bugzilla-daemon [this message]
2011-09-16 13:21 ` [Bug 40931] r600g: interpret integer texture types as ints regresses VDPAU/XVMC decode 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
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=bug-40931-502@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 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.