From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97477] i915g: gl_FragCoord is always (0.0, max_y)
Date: Thu, 25 Aug 2016 05:16:17 +0000 [thread overview]
Message-ID: <bug-97477-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1757 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97477
Bug ID: 97477
Summary: i915g: gl_FragCoord is always (0.0, max_y)
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/i915g
Assignee: dri-devel@lists.freedesktop.org
Reporter: nicholasbishop@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 126029
--> https://bugs.freedesktop.org/attachment.cgi?id=126029&action=edit
Patch: Handle I915_SEMANTIC_POS when setting texCoords for gl_FragCoord
On Intel Pineview M hardware, the i915 gallium driver doesn't output the
correct gl_FragCoord. It seems to always have an X coord of 0.0 and a Y coord
of the window's height in pixels, e.g. 600.0f or such.
I believe this is a regression caused in part by commit
afa035031ff9e0c07a2297d864e46c76f7bfff58
(https://lists.freedesktop.org/archives/mesa-commit/2016-January/061181.html)
The old behavior used output zero, while the new behavior uses actual zeroes.
In the case of gl_FragCoord output zero happened to be the correct one.
I've attached a patch that seems to fix the issue for me. I ran the piglit
"quick" tests and observed 17 new tests passing, and one regression. I suspect
the regression is unimportant since it involves derivatives that aren't
implemented for this driver anyway:
"fs-dfdy-accuracy" test failed ... in i915_fpc_translate.c:
case TGSI_OPCODE_DDY:
/* XXX We just output 0 here */
debug_printf("Punting DDX/DDX\n");
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3563 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-08-25 5:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 5:16 bugzilla-daemon [this message]
2016-08-25 23:34 ` [Bug 97477] i915g: gl_FragCoord is always (0.0, max_y) bugzilla-daemon
2019-09-18 19:31 ` 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-97477-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.