Well, I dug a bit deeper into writing R300 driver (using R200 one to
start with) and I have more questions:
1. What does rmesa->TclFallback do and how should I activate it ?
2. What is "state" ? More specifically:
A) I noticed that state holds contents of a lot of registers,
most of which are not present in R300.
Is there a safe and easy way to to remove their usage ?
B) When is state updated and how ? I assume that it is written
only when registers change - so is marking registers dirty
done by driver only or by Mesa internals too ?
C) I assume I would need to add new registers to the state - any
pointers/suggestions about what needs to be done ?
i) In particular, is their any locking that needs to be
done ?
3. Are functions in r200_cmdbuf and r200_sanity the only ones that
deal with hardware registers ?
thank you !
Vladimir Dergachev
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel