Attachment 90940 Details for Bug 60389 – possible fix

[patch] possible fix

bug60389.diff (text/plain), 1.35 KB, created by Alex Deucher on 2013-12-18 18:09:58 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Alex Deucher

Created: 2013-12-18 18:09:58 UTC

Size: 1.35 KB

patch

obsolete

>diff --git a/drivers/gpu/drm/radeon/ni.c b/drivers/gpu/drm/radeon/ni.c
>index 11aab2a..b8bbef2 100644
>--- a/drivers/gpu/drm/radeon/ni.c
>+++ b/drivers/gpu/drm/radeon/ni.c
>@@ -877,7 +877,6 @@ static void cayman_gpu_init(struct radeon_device *rdev)
> 	case CHIP_ARUBA:
> 	default:
> 		rdev->config.cayman.max_shader_engines = 1;
>-		rdev->config.cayman.max_pipes_per_simd = 4;
> 		rdev->config.cayman.max_tile_pipes = 2;
> 		if ((rdev->pdev->device == 0x9900) ||
> 		    (rdev->pdev->device == 0x9901) ||
>@@ -919,16 +918,19 @@ static void cayman_gpu_init(struct radeon_device *rdev)
> 			rdev->config.cayman.max_simds_per_se = 2;
> 			rdev->config.cayman.max_backends_per_se = 1;
> 		}
>+
>+		rdev->config.cayman.max_pipes_per_simd = 2; //4
>+		rdev->config.cayman.sx_num_of_sets = 2; //4
>+		rdev->config.cayman.max_hw_contexts = 2;//4
>+
> 		rdev->config.cayman.max_texture_channel_caches = 2;
> 		rdev->config.cayman.max_gprs = 256;
> 		rdev->config.cayman.max_threads = 256;
> 		rdev->config.cayman.max_gs_threads = 32;
> 		rdev->config.cayman.max_stack_entries = 512;
>-		rdev->config.cayman.sx_num_of_sets = 8;
> 		rdev->config.cayman.sx_max_export_size = 256;
> 		rdev->config.cayman.sx_max_export_pos_size = 64;
> 		rdev->config.cayman.sx_max_export_smx_size = 192;
>-		rdev->config.cayman.max_hw_contexts = 8;
> 		rdev->config.cayman.sq_num_cf_insts = 2;
> 
> 		rdev->config.cayman.sc_prim_fifo_size = 0x40;

Actions: View | Splinter Review

Attachments on bug 60389: 74349 | 74350 | 74351 | 74352 | 74355 | 74357 | 74358 | 74359 | 74376 | 74377 | 74378 | 88925 | 90247 | 90885 | 90907 | 90928 | 90939 | 90940 | 90949 | 90957 | 90961

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.