All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 47900] New: Sampler does not work with cubemaps in 16-bit component pixel format
Date: Mon, 26 Mar 2012 14:22:46 +0000	[thread overview]
Message-ID: <bug-47900-502@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 47900
           Summary: Sampler does not work with cubemaps in 16-bit
                    component pixel format
    Classification: Unclassified
           Product: Mesa
           Version: 8.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: llyzs@163.com


If a cubemap is created using 16-bit component pixel format like
PIPE_FORMAT_R16G16B16A16_UNORM or PIPE_FORMAT_R16G16B16A16_FLOAT, it will not
be sampled correctly in fragment shader and generate garbage output. Those
16-bit formats works just fine when using in 2D texture, and the cubemap using
8-bit format also works. It's just the combination cubemap+16bit that does not
work.

Any hints?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2012-03-26 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-26 14:22 bugzilla-daemon [this message]
2012-03-27 10:52 ` [Bug 47900] Sampler does not work with cubemaps in 16-bit floating-point pixel format bugzilla-daemon
2012-03-27 10:53 ` bugzilla-daemon
2019-09-18 18:59 ` 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-47900-502@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.