On 4/17/2015 11:42 AM, Dave Gordon wrote:
On 10/04/15 16:54, Todd Previte wrote:
This is the userspace component of the Displayport compliance testing
software requried for compliance testing of the i915 driver. The README
included in the dp_compliance/ directory contains the most up to date
information on the use and operation of the user app.
Signed-off-by: Todd Previte <tprev...@gmail.com>
---
dp_compliance/README | 102 ++++++
Just one small but important typo I noticed in this file ...
dp_compliance/build.sh | 6 +
dp_compliance/dp_compliance.c | 782 ++++++++++++++++++++++++++++++++++++++++++
dp_compliance/input.c | 48 +++
4 files changed, 938 insertions(+)
create mode 100644 dp_compliance/README
create mode 100755 dp_compliance/build.sh
create mode 100644 dp_compliance/dp_compliance.c
create mode 100644 dp_compliance/input.c
diff --git a/dp_compliance/README b/dp_compliance/README
new file mode 100644
index 0000000..1ef4913
--- /dev/null
+++ b/dp_compliance/README
@@ -0,0 +1,102 @@
+
+Displayport Compliance Testing
+Userspace Application
+
+This is the userspace portion of the Displayport Compliance testing suite for
the
+i915 driver. It must be running in order to successfully complete Displayport
+compliance testing. This file contains the latest available information about
+the user app and its operation.
+
+This app and the kernel code that accompanies it has been written to satisfy
the
+requirements of the Displayport Link CTS Core 1.2 rev1.1 specification from
VESA.
+
+Note that this application does not support eDP compliance testing.
+
+Compliance testing requires several components:
+ - A kernel build that contains the patch set for DP compliance support
+ - A Displayport compliance testing appliance such as the Unigraf
DPR-100,
+ DPR-120 or Quantum Data 882EDP
+ - This user application
+ - A Windows host machine to run the test software
+ - Root access on the DUT
+
+Test setup:
+ It is strongly recommended that the Windows host, test appliance and
DUT be freshly
+ restarted before testing begins. This ensures that any previous
configurations and
+ settings will not interfere with the test process. Refer to the test
appliance
+ documentation for setup, software installation and operation specific
to that
+ device.
+
+ The Linux DUT must be in text (console) mode and cannot have any other
display
+ manager running. The easiest way to accomplish this is to place the
word “text”
+ on the command line for booting the kernel. The recommended boot
parameters for
+ the kernel are as follows:
+ “test debug drm.debug=0x0e”
s/test/text/
.Dave.
Good catch, Dave, thank you! I'll get that fixed immediately.
-T
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
