From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 68402] Some elements are only rendered in top-left area
Date: Fri, 23 Aug 2013 00:16:42 +0000 [thread overview]
Message-ID: <bug-68402-8800-cPmc9FiJVE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68402-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1547 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=68402
--- Comment #4 from Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
You're a star Ján
Just had a word with our main dev and he suggested that
viewport transformation is optional, whereas viewport clip rectangle must be
set before and after 3d_blit().
With that said, here is what can be done to double-check/fix this - note a
quick piglit [1] test before and after each one, plus testing of other games/gl
apps is essential.
* nuke the viewport clip rectangle (despite all odds)
* change the viewport clip rectangle - traceback and use the original values
(the ones saved at the begingin on 3d_blit() and restored at the end)
* nuke the viewport transformation
* add the conditional NV50_TIC_5_LAST_LEVEL__MASK on tic[5] in
nvc0_create_texture_view (compare vs nv50_create_texture_view)
I'm hoping that one of the last two will do the job, although chances are that
it may be one of the first two. Either way a piglit and further testing will
prove which solution is the most appropriate.
Feel free to give it a shot yourself, as it will take a some time until I get
to it(apart from the lack of HW).
Note: depending on your luck(and other unknown to me factors) piglit may lockup
X and your system. Normally a s2r cycle is sufficient to get it back into
shape, otherwise a reboot is needed.
Cheers,
Emil
[1] http://cgit.freedesktop.org/piglit/
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2363 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2013-08-23 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 20:49 [Bug 68402] New: Some elements are only rendered in top-left area bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-68402-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-08-21 20:51 ` [Bug 68402] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 21:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 23:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 0:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-09-02 15:42 ` 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-68402-8800-cPmc9FiJVE@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox