[Dri-devel] TDFX texture assert(t->range[0])

[Michael <le...@nt...>]

Looking at the tdfx driver texture stuff

tdfxTMFindOldestObject 
	does an assert ( t->range[0] ) which afaict is bogus, that's the
	point where it fails here running q3 with hardcoded 1mb of
	texture space.

	a) afaict assert()ing will crash/hang the X server regardless as
	locks are held in the texture functions? Certainly running
	remotely the program assert()s and exits with signal 6, the
	machine in the other room appears locked but a ctrl-c remotely
	and everything carries on.

	b) Changing the assert to an if ( ! range[0] ) tdfxTMDumpTexMem shows lots
	of textures allocated to unit 1 with range[0] == null - this
	surely isn't a bug, is it? If it isn't, the asserts are wrong and
	probably just need removing (or at least some logic to tidy up
	and exit cleanly)

	c) Removing the assert() altogether and I've had q3 running with
	1mb texture mem for a couple of hours. It probably makes sense
	to change the 2d driver to disable DRI if there's less than 256
	* 256 * (2 or num tmus) * (2 or cpp?) as it probably does make
	sense to disable if you can't allocate at least
	1 texture to each tmu though.

-- 
Michael.