From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27704] [KMS] fbo_firecube broken on rv280 and current mesa
Date: Wed, 16 Jan 2013 16:28:36 +0000 [thread overview]
Message-ID: <bug-27704-502-rT4zgubjQD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-27704-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2195 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=27704
--- Comment #8 from smoki <smoki00790@gmail.com> ---
On Fri, Jan 11, 2013 at 6:37 AM, smoki <smoki00790 at gmail.com> wrote:
> Piglit passes more fbo tests on rv280, 14/28 before and now 28/33.
> Also should fix bug:
> https://bugs.freedesktop.org/show_bug.cgi?id=27704
Does this regress anything in piglit? It's been a while since I
looked at this code, I think the issue may be that r1xx/r2xx asics
only support ARGB render buffers while the texture hardware supports
both ARGB and RGBA formats so you may run into cases where you can
texture from a buffer, but can't render to it, at least not without an
intermediate blit to convert the format first.
Alex
-----------------------------------------------------------------------
I am not member on the mesa dev list, so to quick answer here :).
No, no regress in piglit i've seen at all, only better... i even played whole
Drawn 2 game:
http://www.drawngame.com/games/dark-flight
under wine in OpenGL mode, it works perfectly now, needs culling under fbo
which is fixed now and this fix to display text and so works exactly the same
as with nvidia on Windows.
It can further pass 2 more test in piglit if those are ported from intel:
fbo-nodepth-test
http://cgit.freedesktop.org/mesa/mesa/commit/?id=4d4f2daefabdc4ca1dd778a9265475c65ef52936
i've tried that one and it pass and maybe this for fbo-cubemap - but not
tried:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=80513ec8b4c812b9c6249cc5824337a5f04ab34c
Now i checked supertuxkart game, it has some problems with alpha in XRGB8888
format. Under non-fbo mode kart model have black background, and under fbo
models are transparent. I fixed it for non fbo case with
R200_TXFORMAT_ALPHA_IN_MAP for XRGB8888 also in r200_blit, but don't know where
is this format controled for fbos? I mentoioned this because text is slightly
transparent also in that Drawn game, it only works with with fbo extension in
opengl mode, i guess that needs the same fix for XRGB8888 format to expect
alpha under fbo, etc... But OK that can be another bug :).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3432 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
next prev parent reply other threads:[~2013-01-16 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 18:44 [Bug 27704] New: [KMS] fbo_firecube broken on rv280 and current mesa bugzilla-daemon
2010-05-03 8:16 ` [Bug 27704] " bugzilla-daemon
2013-01-11 2:26 ` bugzilla-daemon
2013-01-11 2:43 ` bugzilla-daemon
2013-01-11 2:45 ` bugzilla-daemon
2013-01-11 9:50 ` bugzilla-daemon
2013-01-11 10:07 ` bugzilla-daemon
2013-01-11 14:41 ` bugzilla-daemon
2013-01-16 16:28 ` bugzilla-daemon [this message]
2013-01-16 16:37 ` 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-27704-502-rT4zgubjQD@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;
as well as URLs for NNTP newsgroup(s).