From: Todd Previte <tprevite@gmail.com>
To: Dave Gordon <david.s.gordon@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] igt/dp: Displayport Compliance Testing - Userspace Component
Date: Fri, 17 Apr 2015 11:45:05 -0700 [thread overview]
Message-ID: <553154B1.1060607@gmail.com> (raw)
In-Reply-To: <55315413.3050808@intel.com>
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 <tprevite@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
prev parent reply other threads:[~2015-04-17 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 15:54 [intel-gfx][PATCH] Displayport Compliance User Application Todd Previte
2015-04-10 15:54 ` [PATCH] igt/dp: Displayport Compliance Testing - Userspace Component Todd Previte
2015-04-17 13:44 ` Thomas Wood
2015-04-17 17:52 ` Todd Previte
2015-04-20 14:13 ` Thomas Wood
2015-04-17 18:42 ` Dave Gordon
2015-04-17 18:45 ` Todd Previte [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=553154B1.1060607@gmail.com \
--to=tprevite@gmail.com \
--cc=david.s.gordon@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox