From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 110897] HyperZ is broken for r300 (bad z for some micro and macrotiles?) Date: Sat, 15 Jun 2019 15:20:59 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0518290641==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 56E578901E for ; Sat, 15 Jun 2019 15:20:59 +0000 (UTC) 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 --===============0518290641== Content-Type: multipart/alternative; boundary="15606120594.330ED6E.15972" Content-Transfer-Encoding: 7bit --15606120594.330ED6E.15972 Date: Sat, 15 Jun 2019 15:20:59 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D110897 --- Comment #48 from Richard Thier --- Btw I saw that mesa codes handle my RC410 as one having RV350 (is_rv350 is true), but unlike R400 family chip. I have no idea if that is right, but if= the kernel part do differently than the userland part that is clearly wrong tha= t is sure! I kind of have a feeling this card is closer to R300 family than R400, but these are the questions that I have problems answering myself :-( In any ways. I think the wrong rXX_start function is called and r300_start shoud have been called instead in my case originally... Now I am looking wh= ere to fix this as it seems like an easy patch after properly finding the issue source. Actually if this is the case I am only lucky that this manifests itself onl= y in this subtle details because that means a whole minor family different code = is running for my card and it takes only luck that it works... --=20 You are receiving this mail because: You are the assignee for the bug.= --15606120594.330ED6E.15972 Date: Sat, 15 Jun 2019 15:20:59 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 48 on bug 11089= 7 from = Richard Thier 
Btw I saw that mesa codes handle my RC410 as one having RV350 =
(is_rv350 is
true), but unlike R400 family chip. I have no idea if that is right, but if=
 the
kernel part do differently than the userland part that is clearly wrong tha=
t is
sure!

I kind of have a feeling this card is closer to R300 family than R400, but
these are the questions that I have problems answering myself :-(

In any ways. I think the wrong rXX_start function is called and r300_start
shoud have been called instead in my case originally... Now I am looking wh=
ere
to fix this as it seems like an easy patch after properly finding the issue
source.

Actually if this is the case I am only lucky that this manifests itself onl=
y in
this subtle details because that means a whole minor family different code =
is
running for my card and it takes only luck that it works...

You are receiving this mail because:
  • You are the assignee for the bug.
= --15606120594.330ED6E.15972-- --===============0518290641== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0518290641==--