On Thu, 19 Feb 2004 18:58:25 -0300
Rafael Maximo <[EMAIL PROTECTED]> wrote:

[snip]
> 
> I really interested on helping, specially on savage4 driver because is the 
> only one i have access, unfortunately i don't have much experience on 
> hardware programing but i'm learning a lot checking the savage source and 
> i'll try to help in anyway a can.

I think you should definitely start with fixing smaller problems so you
get used to the source code. These two can be done on savage4:

- disable hardware culling for lines and points
- fix LOD bias

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?

For the hardware culling problem you'd need to get an understanding of
how savagetris.c and the templates that it uses work. That may take some
time to get into. Also comparison with other drivers, especially r128
and mga, may be helpful.

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_id=1356&alloc_id=3438&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to