From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 57875] Second Life viewer bad rendering with git-ec83535
Date: Thu, 06 Dec 2012 23:43:23 +0000 [thread overview]
Message-ID: <bug-57875-502-WBNVwAxZvb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-57875-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1388 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=57875
--- Comment #14 from Marek Olšák <maraeo@gmail.com> ---
(In reply to comment #10)
> > That bit only exists on r5xx asics. R3xx and r4xx don't have that bit.
> I'd say it's related to floating point depth buffer support. I don't know
> about the capabilities of the GPUs though and have to read up the
> interactions between depth_clamp and depth_buffer_float again, but I'd
> expect the limited depth buffer range to clamp the values.
There's no floating-point depth buffer support in r500.
> > I don't remember having anything useful besides some quick hacks and I don't
> > have them anymore.
> I've written a kernel hack, now the broken geometry is mostly behind the
> correct parts. I guess this is where you stopped last time.
>
> Before I give up on this I'd like to investigate some more things,
> particularly the interaction with glDepthRange(something similar to
> 92e7c6a2581b5f612a84587500399bb00318c6f0) and the interactions with and the
92e7c6a258 fixes a piglit test which passes with r300g, so it's most probably
unrelated.
glDepthRange is packed in the Z component of the vectors in
pipe_viewport_state, which is applied after clipping and converts coordinates
from the clip space to the window space.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2324 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-12-06 23:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 13:04 [Bug 57875] New: Second Life viewer bad rendering with git-ec83535 bugzilla-daemon
2012-12-04 13:08 ` [Bug 57875] " bugzilla-daemon
2012-12-04 13:11 ` bugzilla-daemon
2012-12-04 13:53 ` bugzilla-daemon
2012-12-06 15:55 ` bugzilla-daemon
2012-12-06 16:54 ` bugzilla-daemon
2012-12-06 17:04 ` bugzilla-daemon
2012-12-06 17:09 ` bugzilla-daemon
2012-12-06 18:20 ` bugzilla-daemon
2012-12-06 18:34 ` bugzilla-daemon
2012-12-06 18:52 ` bugzilla-daemon
2012-12-06 18:55 ` bugzilla-daemon
2012-12-06 20:49 ` bugzilla-daemon
2012-12-06 22:03 ` bugzilla-daemon
2012-12-06 23:43 ` bugzilla-daemon [this message]
2012-12-09 21:59 ` bugzilla-daemon
2012-12-10 15:20 ` bugzilla-daemon
2012-12-12 20:29 ` bugzilla-daemon
2012-12-27 10:25 ` bugzilla-daemon
2013-01-07 15:43 ` bugzilla-daemon
2013-01-07 16:12 ` bugzilla-daemon
2013-01-21 19:07 ` bugzilla-daemon
2013-01-21 22:16 ` bugzilla-daemon
2013-01-22 10:25 ` bugzilla-daemon
2013-01-22 10:39 ` bugzilla-daemon
2013-01-25 11:27 ` bugzilla-daemon
2013-03-13 13:30 ` bugzilla-daemon
2013-03-13 21:20 ` bugzilla-daemon
2013-06-30 16:07 ` bugzilla-daemon
2013-07-01 15:15 ` bugzilla-daemon
2013-07-16 12:43 ` bugzilla-daemon
2013-07-16 13:40 ` bugzilla-daemon
2013-07-16 17:09 ` bugzilla-daemon
2013-07-30 21:12 ` 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-57875-502-WBNVwAxZvb@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;
as well as URLs for NNTP newsgroup(s).