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 30152] New: [r300g] kwin blur effect is not working
Date: Sun, 12 Sep 2010 19:21:07 -0700 (PDT)	[thread overview]
Message-ID: <bug-30152-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [r300g] kwin blur effect is not working
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: tstellar@gmail.com


Original discussion started here:
https://bugs.freedesktop.org/show_bug.cgi?id=30007#c17

Piglit testcase:
https://bugs.freedesktop.org/attachment.cgi?id=38652

I'm not sure exactly what the problem is here.  At first glance, this shader
appears to be compiled correctly, so it might be a bug elsewhere in the driver.

-- 
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:[~2010-09-13  2:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13  2:21 bugzilla-daemon [this message]
2010-09-13  7:40 ` [Bug 30152] [r300g] kwin blur effect is not working bugzilla-daemon
2010-09-13  7:45 ` bugzilla-daemon
2010-09-13  7:57 ` bugzilla-daemon
2010-09-14  0:28 ` bugzilla-daemon
2010-09-14  1:08 ` bugzilla-daemon
2010-09-27  2:15 ` bugzilla-daemon
2010-09-28  1:04 ` bugzilla-daemon
2010-09-28  1:34 ` bugzilla-daemon
2010-11-17 15:21 ` bugzilla-daemon
2010-12-14 19:06 ` bugzilla-daemon
2010-12-14 20:44 ` bugzilla-daemon
2010-12-15  7:48 ` bugzilla-daemon
2010-12-17 12:25 ` 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-30152-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox