From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 27179] New: Slight various between software and r600 results in tri and wave in progs/samples
Date: Thu, 18 Mar 2010 10:52:28 -0700 (PDT) [thread overview]
Message-ID: <bug-27179-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=27179
Summary: Slight various between software and r600 results in tri
and wave in progs/samples
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: kdekorte@yahoo.com
Created an attachment (id=34212)
--> (http://bugs.freedesktop.org/attachment.cgi?id=34212)
software on left, hardware on right
I ran the progs/samples/tri and progs/samples/wave mesa examples in software
and hardware mode and found a few problems. I have attached and image where
software mode is on the left and hardware mode is on the right.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next reply other threads:[~2010-03-18 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 17:52 bugzilla-daemon [this message]
2010-12-21 18:05 ` [Bug 27179] Slight various between software and r600 results in tri and wave in progs/samples bugzilla-daemon
2011-03-07 19:16 ` [Bug 27179] [RADEON::R600C] incorrect rendering r600c vs software " bugzilla-daemon
2011-03-07 20:07 ` bugzilla-daemon
2012-02-22 18:01 ` 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-27179-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/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