This patch series implement first part of what i was describing in
a previous mail about ttm. Patches are not yet ready for inclusion
(need to finish commenting new fields & function and pass them
through checkpatch.pl), first patch is likely ready to go in.

It mostly allow driver to give a different preference order on
placement when validating a bo. It also factor some of ttm code
along the way. Finaly it also offer the range validation in
a bit different way than previous patch. Range validation will
be suboptimal but i don't expect range validation to be a common
case (some optimization like one in my previous patch might be
adapted later if this case is important for anyone).

I am mostly seeking for feedback on the API change
ttm-validate
ttm-init-mm

It seems to work without issue on radeon, but haven't done
extensive testing yet, i was chasing a bug due to paste/copy
error.


------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to