Hi all,
I have fixed known issues with r300 DRM driver:
* r300_emit_unchecked_state properly fallbacks to
r300_emit_carefully_checked_state() when asked to set
touchy registers (i.e. those with offsets).
* r300_emit_raw properly checks LOAD_VBPNTR packet that all
offsets are ok.
* all of these copy user data exactly once.
The next step is to discuss what else is needed for successful merge
into the main DRM CVS.
* What are the requirements for a patch to be accepted ?
* Can R300 developers get CVS access ?
* What else do we need in R300 DRM module ?
(Besides working PCIE - Dave what are wishes in this regard ?)
* any issues that I missed ?
thank you !
Vladimir Dergachev
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel
