From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 40936] New: register address overlap make line stipple error
Date: Fri, 16 Sep 2011 05:16:23 -0700 (PDT) [thread overview]
Message-ID: <bug-40936-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=40936
Summary: register address overlap make line stipple error
Product: Mesa
Version: 7.11
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: raoxianhong@163.net
In file r700_chip.c function r700SendSUState:
R600_OUT_BATCH_REGSEQ(PA_SU_POINT_SIZE, 4);
R600_OUT_BATCH(r700->PA_SU_POINT_SIZE.u32All);
R600_OUT_BATCH(r700->PA_SU_POINT_MINMAX.u32All);
R600_OUT_BATCH(r700->PA_SU_LINE_CNTL.u32All);
R600_OUT_BATCH(r700->PA_SU_VTX_CNTL.u32All);
must be:
R600_OUT_BATCH_REGSEQ(PA_SU_POINT_SIZE, 3);
R600_OUT_BATCH(r700->PA_SU_POINT_SIZE.u32All);
R600_OUT_BATCH(r700->PA_SU_POINT_MINMAX.u32All);
R600_OUT_BATCH(r700->PA_SU_LINE_CNTL.u32All);
R600_OUT_BATCH_REGVAL(PA_SU_VTX_CNTL, r700->PA_SU_VTX_CNTL.u32All);
NOTE:
PA_SU_POINT_SIZE ; /* 0xA280 */
PA_SU_POINT_MINMAX ; /* 0xA281 */
PA_SU_LINE_CNTL ; /* 0xA282 */
PA_SU_VTX_CNTL ; /* 0xA302 */
PA_SC_LINE_STIPPLE ; /* 0xA283 */
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-09-16 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 12:16 bugzilla-daemon [this message]
2011-09-16 17:19 ` [Bug 40936] register address overlap make line stipple error bugzilla-daemon
2011-09-17 8:38 ` bugzilla-daemon
2012-02-22 18:02 ` bugzilla-daemon
2012-11-02 16:30 ` bugzilla-daemon
2014-07-07 16:05 ` 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-40936-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.