dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89156] r300g: GL_COMPRESSED_RED_RGTC1 / ATI1N support broken
Date: Thu, 26 Feb 2015 11:46:17 +0000	[thread overview]
Message-ID: <bug-89156-502-BP9MnGc1FS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89156-502@http.bugs.freedesktop.org/>


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

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

--- Comment #6 from Stefan Dösinger <stefandoesinger@gmx.at> ---
(In reply to Marek Olšák from comment #5)
> So it's a compiler bug.
In which sense? Is there something in the spec that tells me I should expect
garbage when I use texture2D().xxxx? Or is this something the driver tells the
compiler and the compiler is supposed to generate a swizzle-free texture2D
statement?

> > static const char ati1n_data[] =
> > {
> >     /* A 4x4 texture with the color component at 50%. */
> >     0x7f, 0x7f, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
> > };
> 
> That's expected. ATI1N operates at lower precision. I'm afraid I can't
> change that.
Windows gives me a proper value (0x7f, which is pretty close to 0x80). Do you
have any idea how it does that?

I can try to find a scheme behind the imprecision if it helps you. There may be
something like an off by one error that the driver can account for.

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

[-- Attachment #1.2: Type: text/html, Size: 1988 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 11:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 16:28 [Bug 89156] r300g: GL_COMPRESSED_RED_RGTC1 / ATI1N support broken bugzilla-daemon
2015-02-21 10:49 ` bugzilla-daemon
2015-02-24  9:13 ` bugzilla-daemon
2015-02-24 21:38 ` bugzilla-daemon
2015-02-26  9:36 ` bugzilla-daemon
2015-02-26 11:23 ` bugzilla-daemon
2015-02-26 11:46 ` bugzilla-daemon [this message]
2015-02-26 13:26 ` bugzilla-daemon
2015-03-02 13:34 ` bugzilla-daemon
2015-03-02 13:50 ` bugzilla-daemon
2015-03-02 14:12 ` bugzilla-daemon
2015-03-09 20:05 ` 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-89156-502-BP9MnGc1FS@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).