All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89148] r300g: Kernel rejected CS in Wine d3d multisample test
Date: Thu, 26 Feb 2015 09:48:56 +0000	[thread overview]
Message-ID: <bug-89148-502-wMeAjr08QX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89148-502@http.bugs.freedesktop.org/>


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

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

--- Comment #11 from Stefan Dösinger <stefandoesinger@gmx.at> ---
Attachment 113802 fixes the invalid CS / crash and my test program now reads a
color. However, sRGB color correction seems to be applied at some stage. Note
that the test program is not using GL_ARB_framebuffer_sRGB (which isn't
supported on r500 anyway), and that GL_TEXTURE_SRGB_DECODE_EXT is set to
GL_SKIP_DECODE_EXT.

It seems that the correction is applied during blitting. If I clear the 2D
texture directly the expected result (0x0000ff80) is returned. If I use the
renderbuffer and blit I get 0x0000ff37.

(Wine expects that glBlitFramebuffer never applies sRGB correction when
blitting from an sRGB texture, but this codepath is only used if
GL_EXT_sRGB_decode is not supported. In this case we load two copies of the
texture, one sRGB and one RGB, and use glBlitFramebuffer to blit between them
if the application toggles sRGB on and off.)

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

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

  parent reply	other threads:[~2015-02-26  9:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-14 16:26 [Bug 89148] r300g: Kernel rejected CS in Wine d3d multisample test bugzilla-daemon
2015-02-14 16:32 ` bugzilla-daemon
2015-02-16 19:18 ` bugzilla-daemon
2015-02-17  9:36 ` bugzilla-daemon
2015-02-17 11:43 ` bugzilla-daemon
2015-02-18 15:19 ` bugzilla-daemon
2015-02-21 11:06 ` bugzilla-daemon
2015-02-21 12:01 ` bugzilla-daemon
2015-02-21 12:10 ` bugzilla-daemon
2015-02-24  8:59 ` bugzilla-daemon
2015-02-24 22:23 ` bugzilla-daemon
2015-02-26  9:48 ` bugzilla-daemon [this message]
2015-02-26 11:17 ` bugzilla-daemon
2015-02-26 12:00 ` bugzilla-daemon
2015-03-10 10:36 ` 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-89148-502-wMeAjr08QX@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 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.