All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 57875] Second Life viewer bad rendering with git-ec83535
Date: Mon, 10 Dec 2012 15:20:48 +0000	[thread overview]
Message-ID: <bug-57875-502-frjVHYeqAH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-57875-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1337 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=57875

--- Comment #16 from Henri Verbeet <hverbeet@gmail.com> ---
(In reply to comment #15)
> I've written an extension proposal for a new mesa extension that exposes the
> CLIP_DISABLE bit. The proposal is attached, please review and comment. There
> are some TODOs I'm not quite sure how to deal with, see the list in "Status".
> 
  - It probably makes sense to mention "depth" in the extension name somewhere,
we really only care about the near and far clipping planes. E.g.
MESA_depth_clip.
  - Perhaps it makes more sense to write the extension in terms of
ARB_depth_clamp. I.e., provide a subset of ARB_depth_clamp, that only disables
depth clipping, and generates undefined results in the depth test, except for
perhaps GL_ALWAYS / GL_NEVER. (Also, note that you can't really make fragment
depth values undefined before / in the fragment shader, because you have
interactions with e.g. texture filtering as well.) It would avoid the perhaps
somewhat questionable "ARB_depth_clamp must not be supported", and you can just
defer to ARB_depth_clamp for most of the issues etc. The interaction between
the two extensions just becomes that if ARB_depth_clamp is also supported you
get defined depth test results.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2221 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

  parent reply	other threads:[~2012-12-10 15:20 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
2012-12-09 21:59 ` bugzilla-daemon
2012-12-10 15:20 ` bugzilla-daemon [this message]
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-frjVHYeqAH@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.