Attachment 38951 Details for Bug 30313 – possible fix

[patch] possible fix

0001-r300g-attempt-to-fix-tiling-on-R350.patch (text/plain), 1.34 KB, created by Marek Olšák on 2010-09-25 06:02:49 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Marek Olšák

Created: 2010-09-25 06:02:49 UTC

Size: 1.34 KB

patch

obsolete

>From a85a08bc13d4e8cd4e30af85cf7d1674e258fdcb Mon Sep 17 00:00:00 2001
>From: =?UTF-8?q?Marek=20Ol=C5=A1=C3=A1k?= <maraeo@gmail.com>
>Date: Sat, 25 Sep 2010 14:57:32 +0200
>Subject: [PATCH] r300g: attempt to fix tiling on R350
>
>---
> src/gallium/drivers/r300/r300_texture_desc.c |    4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/src/gallium/drivers/r300/r300_texture_desc.c b/src/gallium/drivers/r300/r300_texture_desc.c
>index 20d1fda..6a1030f 100644
>--- a/src/gallium/drivers/r300/r300_texture_desc.c
>+++ b/src/gallium/drivers/r300/r300_texture_desc.c
>@@ -256,7 +256,7 @@ static void r300_setup_miptree(struct r300_screen *screen,
> {
>     struct pipe_resource *base = &desc->b.b;
>     unsigned stride, size, layer_size, nblocksy, i;
>-    boolean rv350_mode = screen->caps.is_rv350;
>+    boolean rv350_mode = screen->caps.family >= CHIP_FAMILY_R350;
>     boolean aligned_for_cbzb;
> 
>     desc->size_in_bytes = 0;
>@@ -351,7 +351,7 @@ static void r300_setup_tiling(struct r300_screen *screen,
> {
>     struct r300_winsys_screen *rws = screen->rws;
>     enum pipe_format format = desc->b.b.format;
>-    boolean rv350_mode = screen->caps.is_rv350;
>+    boolean rv350_mode = screen->caps.family >= CHIP_FAMILY_R350;
>     boolean is_zb = util_format_is_depth_or_stencil(format);
>     boolean dbg_no_tiling = SCREEN_DBG_ON(screen, DBG_NO_TILING);
> 
>-- 
>1.7.0.4
>

Actions: View | Splinter Review

Attachments on bug 30313: 38848 | 38849 | 38850 | 38851 | 38852 | 38951 | 38963 | 38964 | 38965 | 38966 | 38967 | 38968 | 38969 | 38970

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.