From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 54877] [bisected] rendering corrupted for windows larger than 2048 pixels in one dimension
Date: Fri, 14 Sep 2012 13:47:19 +0000 [thread overview]
Message-ID: <bug-54877-502-Xe9upuag1M@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-54877-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=54877
--- Comment #4 from Alex Deucher <agd5f@yahoo.com> 2012-09-14 13:47:19 UTC ---
(In reply to comment #3)
> (In reply to comment #2)
> > Created attachment 67121 [details] [review] [review]
> > fix
> >
> > This fixes it. I need to find out how the quant mode affects the range of
> > values.
>
> My guess is that QUANT_MODE determines the position of fixed point for internal
> calculations in hw. Quantization precision 1/4096 means 12 bits, and it looks
> like we have 11 bits before the point in that case, with 23 bits total. So if
> we need to increase the range, we have to move the point lowering the
> precision.
>
> I've tried 1/256 and other values on evergreen for initial implementation of
> that patch in hope that it'll be enough, but IIRC 1/4096 fixed more tests
> (though possibly some test results were simply random). If some tests are
> really failing due to lower precision, I guess we might want to adjust
> QUANT_MODE dynamically.
That makes sense. The hw worked similarly on r300-r500. We should adjust the
mode based on the size of the buffer I suppose.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-09-14 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 15:36 [Bug 54877] New: [bisected] rendering corrupted for windows larger than 2048 pixels in one dimension bugzilla-daemon
2012-09-13 16:27 ` [Bug 54877] " bugzilla-daemon
2012-09-13 21:30 ` bugzilla-daemon
2012-09-14 6:35 ` bugzilla-daemon
2012-09-14 13:47 ` bugzilla-daemon [this message]
2019-09-18 19:00 ` 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-54877-502-Xe9upuag1M@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