Or add the test params after/under the resolution on the top.
Printable View
Or add the test params after/under the resolution on the top.
Would be tough to generalize all of that needed information in a fully automated manner since pts-core wouldn't know what is important to scan and find in a test profile to report... Especially with all game config files being different, etc. Anything not fully automated I won't do unless someone provides me with all of the necessary patches.
Instead anyone who really cares about those details outside of a PTS environment can click the title of the graph and get to the test profile page on OpenBenchmarking.org and view the test profile information or the raw profile itself.
I'm with Michael on this, I don't want to have a paragraph of test details on top of every graph, and don't see any simple way of determining exactly which are the important ones to show for each test.
Perhaps that could be built directly into the test profile, so that it could determine a specified information line to add to all graphs based on that test?
What about varying resolutions?
Why is phoronix still peddling this drivel that the new catalyst 2d acceleration is "derived from windows 2d code paths" or derived from direct2d. I recall bridgeman himself saying that the new architecture (ATI 2D Acceleration Architecture) has nothign to do with windows in the slightest.
The switch for enabling it was simply a re-used direct2d development switch, the architecture itself has nothing to do with it.