Bug 7260

Summary: mach64 texture memory mng cleanup
Product: Mesa Reporter: George - <fufutos610>
Component: Drivers/DRI/Mach64Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high CC: alexdeucher
Version: gitKeywords: patch
Hardware: x86 (IA32)   
OS: Linux (All)   
i915 platform: i915 features:
Attachments: use dri/common/texmem.c
use dri/common/texmem.c
use dri/common/texmem.c - try 2
use dri/common/texmem.c - try 3
use dri/common/texmem.c - try 4

Description George - 2006-06-17 12:15:47 UTC
mach64 uses its own set of texture memory management routines.

this bug ports the mach64 code to the stock dri texture managment code.
Comment 1 George - 2006-06-17 12:20:41 UTC
Created attachment 5959 [details] [review]
use dri/common/texmem.c

This is my current diff. The current mach64 code is buggy, running a second DRI
client kills the first one. This patch fixes this by deletion. It removes ~480
Comment 2 George - 2006-06-18 14:36:37 UTC
Created attachment 5967 [details] [review]
use dri/common/texmem.c

This is basically same as yesterday's patch with some cosmetic changes and a
minor fix for c_textureSwaps from PERF_BOXES.
Comment 3 George - 2006-06-20 08:55:14 UTC
Created attachment 5993 [details] [review]
use dri/common/texmem.c - try 2

This patch updates mach64UploadMultiTexImages() (for collocating two textures
in the same heap) to always try the AGP heap. This is as far as I am willing to
go and I think its at least as good as it was. So, I think this patch is ready
for review.
Comment 4 George - 2006-06-22 08:45:37 UTC
Created attachment 6018 [details] [review]
use dri/common/texmem.c - try 3

minor cosmetic.
Comment 5 George - 2006-10-07 01:59:19 UTC
Created attachment 7277 [details] [review]
use dri/common/texmem.c - try 4

"rebase" to head.
Comment 6 George - 2006-12-12 02:57:21 UTC
commited (5b35132b41427798e02a66a8e39583fffbe9d232)
Comment 7 Adam Jackson 2009-08-24 12:23:59 UTC
Mass version move, cvs -> git

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.