From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28606] [r300g]: Compiz focus blur effect does not work. (causes black windows instead)
Date: Sat, 3 Jul 2010 16:34:57 -0700 (PDT) [thread overview]
Message-ID: <20100703233457.506ED1300FB@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-28606-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=28606
--- Comment #4 from Marek Olšák <maraeo@gmail.com> 2010-07-03 16:34:57 PDT ---
The real problem with the r300 compiler is scheduling of TEX blocks, which is
done against the r300 hardware (r500 is ok here). I've had a closer look at a
shader from etqw which creates about 10 TEX blocks on r300 even though there
are NO texture indirections. The instructions just have wrong ordering and that
is the only reason the shader doesn't fit in hardware.
--
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:[~2010-07-03 23:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 21:48 [Bug 28606] New: [r300g]: Compiz focus blur effect does not work. (causes black windows instead) bugzilla-daemon
2010-06-18 21:56 ` [Bug 28606] " bugzilla-daemon
2010-06-18 21:58 ` bugzilla-daemon
2010-07-03 20:56 ` bugzilla-daemon
2010-07-03 20:57 ` bugzilla-daemon
2010-07-03 23:34 ` bugzilla-daemon [this message]
2010-07-04 23:54 ` bugzilla-daemon
2010-07-05 16:30 ` bugzilla-daemon
2010-07-05 23:28 ` bugzilla-daemon
2010-07-06 1:06 ` bugzilla-daemon
2010-07-07 18:33 ` bugzilla-daemon
2010-07-07 18:34 ` bugzilla-daemon
2010-07-07 20:15 ` bugzilla-daemon
2010-07-07 20:30 ` bugzilla-daemon
2010-07-08 21:49 ` bugzilla-daemon
2010-07-09 4:39 ` 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=20100703233457.506ED1300FB@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 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.