path: root/README.md
diff options
authorCNLohr <charles@cnlohr.com>2017-03-19 16:55:54 -0400
committerGitHub <noreply@github.com>2017-03-19 16:55:54 -0400
commita229dec7ee46873e0b590fdbd34feb29112e4f0d (patch)
tree56ec0e8d064e908336fbdfd67710c4b486a599a7 /README.md
parentaaaa45dcd79e1d9ebe04ec428422fa29d1961488 (diff)
Update README.md
Diffstat (limited to 'README.md')
1 files changed, 6 insertions, 0 deletions
diff --git a/README.md b/README.md
index 7b89c2d..db1d6ce 100644
--- a/README.md
+++ b/README.md
@@ -77,3 +77,9 @@ I may or may not read data from the Vive regarding configuration. If I do, it w
The limiting factor for Vive viability on a given computer is the maximum available pixel clock frequency, and frequency limitations of the HDMI port, and HDMI and DisplayPort video cables. DisplayPort can support higher frequencies than HDMI, on Ivy Bridge HD4000 graphics. In fact, the Vive works with HD4000 graphics using DisplayPort, with native EDID resolution (2160x1200@90Hz).
To support the Vive on HDMI, you either need a newer version of HDMI, or you need to define a custom resolution that respects pixel clock and video port limits, and is also accepted and displayed by the Vive. So far, we have not had success using custom resolutions on linux or on Windows. Windows imposes additional limitations in the form of restriction of WHQL certified drivers forbidden from using custom display resolutions (only allowing those defined by EDID in the monitor). Intel has released uncertified beta drivers for Haswell and newer processors, which should be able to support custom resolutions for the Vive (untested at this time).
+## Addendum and notes
+Thanks to Mr. Fault for our logo!