From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36965] GL_EXT_texture_sRGB (included in OpenGL 2.1) is broken (glean/texture_srgb broken too)
Date: Thu, 12 May 2011 14:08:00 -0700 (PDT) [thread overview]
Message-ID: <20110512210800.1CDAB13004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-36965-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=36965
--- Comment #5 from Pavel Ondračka <pavel.ondracka@email.cz> 2011-05-12 14:07:59 PDT ---
(In reply to comment #4)
> There is a lot of other code which plays role in handling sRGB textures. I
> don't think getteximage.c is relevant to this issue(s).
>
> Nevertheless, it looks like Pavel's and Martin's issues are different bugs.
>
> Pavel reported that GL_EXT_texture_sRGB_decode, which is only in 7.11, is
> broken specifically on r300g, but other drivers might be affected as well and
> it definitely looks like a Mesa core bug. Pavel, could you please add it as a
> new bug against Mesa core?
>
Reported against mesa core as bug 37150.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-05-12 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 14:00 [Bug 36965] New: GL_EXT_texture_sRGB (included in OpenGL 2.1) is broken bugzilla-daemon
2011-05-12 16:11 ` [Bug 36965] " bugzilla-daemon
2011-05-12 16:18 ` bugzilla-daemon
2011-05-12 17:20 ` bugzilla-daemon
2011-05-12 19:50 ` [Bug 36965] GL_EXT_texture_sRGB (included in OpenGL 2.1) is broken (glean/texture_srgb broken too) bugzilla-daemon
2011-05-12 21:08 ` bugzilla-daemon [this message]
2012-11-02 10:37 ` bugzilla-daemon
2012-11-02 11:55 ` bugzilla-daemon
2012-11-02 12:13 ` 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=20110512210800.1CDAB13004E@annarchy.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).