Update README

Signed-off-by: Thomas Wood <thomas.wood@intel.com>
This commit is contained in:
Thomas Wood 2014-10-29 11:18:27 +00:00
parent 5d46f68eab
commit 84f23415c4

44
README
View File

@ -1,17 +1,22 @@
This is a collection of tools for development and testing of the Intel DRM Intel GPU Tools
driver. There are many macro-level test suites that get used against our ===============
driver, including xtest, rendercheck, piglit, and oglconform, but failures
Description
-----------
Intel GPU Tools is a collection of tools for development and testing of the
Intel DRM driver. There are many macro-level test suites that get used against
the driver, including xtest, rendercheck, piglit, and oglconform, but failures
from those can be difficult to track down to kernel changes, and many require from those can be difficult to track down to kernel changes, and many require
complicated build procedures or specific testing environments to get useful complicated build procedures or specific testing environments to get useful
results. results. Therefore, Intel GPU Tools includes low-level tools and tests
specifically for development and testing of the Intel DRM Driver.
Thus, intel-graphics-tools was a project I started to collect some low-level Intel GPU Tools is split into several sections:
tools I intended to build.
benchmarks/ benchmarks/
This should be a collection of useful microbenchmarks. The hope is This is a collection of useful microbenchmarks that can be used to tune
that people can use these to tune some pieces of DRM code in relevant DRM code in relevant ways.
ways.
The benchmarks require KMS to be enabled. When run with an X Server The benchmarks require KMS to be enabled. When run with an X Server
running, they must be run as root to avoid the authentication running, they must be run as root to avoid the authentication
@ -21,8 +26,11 @@ benchmarks/
tests/ tests/
This is a set of automated tests to run against the DRM to validate This is a set of automated tests to run against the DRM to validate
changes. Hopefully this can cover the relevant cases we need to changes. Many of the tests have subtests, which can be listed by using
worry about, including backwards compatibility. the --list-subtests command line option and then run using the
--run-subtest option. If --run-subtest is not used, all subtests will
be run. Some tests have futher options and these are detailed by using
the --help option.
The test suite can be run using the run-tests.sh script available in The test suite can be run using the run-tests.sh script available in
the scripts directory. Piglit is used to run the tests and can either the scripts directory. Piglit is used to run the tests and can either
@ -115,9 +123,10 @@ debugger/
The debugger must be run as root: "sudo debugger/eudb" The debugger must be run as root: "sudo debugger/eudb"
docs/ docs/
Thus far just contains the autogenerated intel-gpu-tools libraries Contains the automatically generated intel-gpu-tools libraries
reference documenation in docs/reference/ You need to have the gtk doc reference documentation in docs/reference/. You need to have the
tools installed to generate this API documentation. gtk-doc tools installed and use the "--enable-gtk-doc" configure flag
to generate this API documentation.
To regenerate the html files when updating documentation, use: To regenerate the html files when updating documentation, use:
@ -128,8 +137,11 @@ docs/
intel-gpu-tools-sections.txt. Entirely new sections will also need to be intel-gpu-tools-sections.txt. Entirely new sections will also need to be
added to intel-gpu-tools-docs.xml in the appropriate place. added to intel-gpu-tools-docs.xml in the appropriate place.
DEPENDENCIES
This is a non-exchaustive list of package dependencies required for Requirements
------------
This is a non-exhaustive list of package dependencies required for
building everything: building everything:
libpciaccess-dev libpciaccess-dev