From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 89156] r300g: GL_COMPRESSED_RED_RGTC1 / ATI1N support broken Date: Mon, 02 Mar 2015 13:50:20 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0627708830==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2BF686E466 for ; Mon, 2 Mar 2015 05:50:20 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0627708830== Content-Type: multipart/alternative; boundary="1425304220.ece10.10878"; charset="UTF-8" --1425304220.ece10.10878 Date: Mon, 2 Mar 2015 13:50:20 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D89156 --- Comment #9 from Stefan D=C3=B6singer --- The reason why I am suspicious about the 3 bits precision and ATI1N is that according to the GPU register docs TX_FMT_ATI1N is separated from TX_FMT_3_= 3_2 only by TX_FORMAT2.TXFORMAT_MSB. Is it possible that some code doesn't look= at TXFORMAT_MSB, thinks it sees TX_FMT_3_3_2 and sets up some other part of the GPU to expect 3 bits of red data? I'm skimming the code for something like this, so far I haven't found anyth= ing. --=20 You are receiving this mail because: You are the assignee for the bug. --1425304220.ece10.10878 Date: Mon, 2 Mar 2015 13:50:20 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Comment= # 9 on bug 89156<= /a> from Stefan D=C3=B6singer
The reason why I am suspicious about the 3 bits precision and =
ATI1N is that
according to the GPU register docs TX_FMT_ATI1N is separated from TX_FMT_3_=
3_2
only by TX_FORMAT2.TXFORMAT_MSB. Is it possible that some code doesn't look=
 at
TXFORMAT_MSB, thinks it sees TX_FMT_3_3_2 and sets up some other part of the
GPU to expect 3 bits of red data?

I'm skimming the code for something like this, so far I haven't found anyth=
ing.


You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1425304220.ece10.10878-- --===============0627708830== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0627708830==--