Am Sonntag, den 08.02.2009, 18:50 -0500 schrieb Alex Deucher:
This looks good, but you might want to look at stalling on a particular vline range rather than vblank in general like we did in the radeon driver. I suppose it's worth comparing which method works better. I thought about that also, but came to the conclusion that an simpler implementation is easier to do right now.
Can i start cleaning up this mess a little bit? For example removing "#define uint32_t CARD32" or the double register definition in rhd_reg.h and r600_reg*.h.
I'm fine with cleaning up. I wanted to move to using std int types originally, but Egbert and others wanted to use CARD* types instead for compatibility with really old compilers that don't support standard int types. AFAIK int*_t and uint*_t are from ISO C99, the problem with this standard is that it's not included in some C++ compiling environments (most noticeable with Microsofts Visual C++, which gives me a constant
My idea was creating a general function with a simple adaptive logic, something like: i want to do an operation which draws (linear) from vertical line y1 to y2, which takes x ms or to be more specific x lines (worse), please time that with the vertical scan out... The problem is that i don't have any idea how to measure how long it takes to make the complete drawing to framebuffer. Any idea for that? headache). Bye, Christian. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org