All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 100177] [GM206] Misrendering in XCOM Ennemy Within
Date: Mon, 13 Mar 2017 02:27:55 +0000	[thread overview]
Message-ID: <bug-100177-8800-V1MNOdhgWG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100177-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #1 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
I have an unproven theory that this is related to polygon-offset failing on
GM20x. Can't figure out what we're missing. In the GM20x traces it seems like
it's jumping through crazy hoops to set all the polygon offset stuff by using a
macro to write out the values. It's effectively conditional on the value in
some scratch register. I suspect it's to be able to apply a CSO without
recomputing it, and adjusting its effect by adjusting scratch registers.
However things are configured s.t. it does do the writes.

One thought is that there's a register somewhere that sets the value of "r",
i.e. the unit of polygon offset. This has traditionally been driven off the
depth format as a function of rasterization details, but perhaps now it's set
explicitly. It'd be 1/1<<24 for Z24, 1/1<<16 for Z16, and "variable" for Z32F.
However no such setting has been found, and there's nothing obvious in the
trace.

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

[-- Attachment #1.2: Type: text/html, Size: 1970 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2017-03-13  2:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 22:37 [Bug 100177] New: [GM206] Misrendering in XCOM Ennemy Within bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-100177-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-03-13  2:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-03-13  4:08   ` [Bug 100177] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-13  4:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-13  9:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 14:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-30 16:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-100177-8800-V1MNOdhgWG@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.