Hello, I committed this on the config branch yesterday but it seems the commit messages didn't get through :-/. So here's a (verbose) summary.
I added two new enum options, one for TCL stuff and one for frame throttling. These two options will replace 5 boolean options. That makes the option list a lot less confusing. TCL mode: - Software (like RADEON_TCL_FORCE_DISABLE) - TCL stage in MESA pipeline (like RADEON_NO_VTXFMT) - Bypass MESA's pipeline (like RADEON_NO_CODEGEN) - Bypass MESA's pipeline with state-specific code generation (full TCL) Frame throttling: - Busy waiting - Usleeps - Software IRQs I've spent some time thinking about the enum case descriptions but I'm still not quite satisfied especially with the TCL stuff. Can anyone think of shorter or clearer ones? I have modified the radeon driver to use these options instead of the old booleans. If noone objects I'm going to do the same for r200. Open issue: what should happen if IRQs are not available and neither usleeps nor busy waiting were explicitly requested? In the trunk radeon driver it will fall back to usleeps unless RADEON_NO_USLEEPS is defined. In the current implementation on the config branch it will fall back to busy waiting. Regards, Felix ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, Kühling (_____\Ä/____/ /_____/ /________) just not everything [EMAIL PROTECTED] \___/ \___/ U at the same time. ------------------------------------------------------- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code=104 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
