On Fri, 20 Feb 2004 08:04:43 -0800 Ian Romanick <[EMAIL PROTECTED]> wrote:
> Felix Kühling wrote: > > > The last one is the easier one I think. In savagetex.c in > > savageUpdateTex0State_s4 and savageUpdateTex1State_s4 there is a pretty > > fancy computation of the 9bit LOD bias (probably some fixed point > > format) from a floating point value. The lodbias mesa demo shows no > > visible change of the LOD bias, so it's either broken in hardware or the > > formula is wrong. Can you try to find a formula that looks right by > > comparing with indirect rendering? > > Or the state isn't being sent to the card correctly. Even if the value > isn't calculated correctly, changing the hardware state should change > what is displayed. Hmm, maybe it forgets to update the state when the LOD bias changes. Once it gets to savageUpdateTex?State_s4 I'm pretty sure the computed value is sent to the hardware correctly. It's in a 32bit words with more flags like filterMode and mipmapEnable. So there would be other visible effects if it wasn't sent to the hardware correctly. Felix ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
