On Wed, 2005-10-12 at 14:58 +0200, Roland Scheidegger wrote: 
> Michel Dänzer wrote:
> > On Wed, 2005-10-12 at 11:01 +0100, pedro.lixo wrote:
> > 
> >>By the way, if i do the override that won't do nothing, in terms of 
> >>amount of memory visible to GPU, right?
> > 
> > No, it will only affect what the driver thinks, and if that doesn't
> > correspond with what's actually there and/or the hardware can handle,
> > bad things will happen, which is why the override is usually bad and the
> > patch you encountered which disables it is generally a good idea.
> Maybe the driver should be changed so it can output a more precise 
> message, so people don't think that the ram is misdetected (e.g. 
> something like "detected 256MB, using 128MB"). 

Yeah, that'd be good.

> Also, the 128MB limit should just not be overridable, since we KNOW the 
> driver can't cope with it (imho, otherwise allowing override is a nice 
> idea, you can for instance simulate performance with cards which have less 
> memory, though you could argue only smaller than detected values are useful, 
> as long as the driver always detects the memory amount correctly).

There's no question that the override is useful for developers, the
question is whether it isn't more harm- than useful for users.

> And, the driver also limits texture memory to only be useable up to 
> 128MB, and I think this is not necessary (as textures are always blitted 
> using the gpu and the memory used by them never touched directly by the 
> cpu) or is it?

Indeed, that memory would probably be useful for textures for now, but
maybe CPU access to textures in the framebuffer will be necessary in the
future?


-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to