dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 57842] r200: Culling is broken when rendering to an FBO
Date: Tue, 04 Dec 2012 20:20:18 +0000	[thread overview]
Message-ID: <bug-57842-502-DGwLACWXtM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-57842-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from Roland Scheidegger <sroland@vmware.com> ---
Hmm this is odd I can't see anything wrong with the culling setup wrt fbos.
The viewport, window handling though seems somewhat bogus.
First, r200UpdateViewportOffset() has no callers (it is used in
radeon->vtbl.update_viewport_offset but that one seems to have no callers
neither). This function would not take the y flip into account but since it
isn't used... I'd just get rid of it but it's the only thing handling stippling
that probably needs to move somewhere else.
Also, both r200UpdateViewportOffset() and r200UpdateWindow() use the
driDrawable height for the yoffset in the viewport. I don't think that will
work for fbos, should just use the ctx->DrawBuffer height instead?
I can't see though why that would just cause failures with culling.

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

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

  reply	other threads:[~2012-12-04 20:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 15:12 [Bug 57842] New: r200: Culling is broken when rendering to an FBO bugzilla-daemon
2012-12-04 20:20 ` bugzilla-daemon [this message]
2012-12-04 20:57 ` [Bug 57842] " bugzilla-daemon
2012-12-05  8:50 ` bugzilla-daemon
2012-12-05  8:51 ` bugzilla-daemon
2012-12-23 23:41 ` bugzilla-daemon
2012-12-24  0:19 ` bugzilla-daemon
2012-12-24  1:04 ` bugzilla-daemon
2012-12-24  1:16 ` bugzilla-daemon
2012-12-24  1:36 ` bugzilla-daemon
2012-12-24  2:18 ` bugzilla-daemon
2012-12-24  2:22 ` bugzilla-daemon
2012-12-24  3:02 ` bugzilla-daemon
2012-12-24  3:38 ` bugzilla-daemon
2012-12-30 22:32 ` bugzilla-daemon
2013-01-02 22:42 ` bugzilla-daemon
2013-01-03  5:14 ` bugzilla-daemon
2013-01-03 14:17 ` bugzilla-daemon
2013-01-03 18: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-57842-502-DGwLACWXtM@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