<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Mode detection fails on Dell Venue 8 Pro (due to bad EDID?)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=74657">74657</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>Mode detection fails on Dell Venue 8 Pro (due to bad EDID?)
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>awilliam@redhat.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>Following on from <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - [BYT] Modesetting on Dell Venue 8 Pro (Bay Trail) produces garbled output (3.11, 3.12) or blank screen (3.13)"
href="show_bug.cgi?id=71977">https://bugs.freedesktop.org/show_bug.cgi?id=71977</a> . With
kernel 3.14-rc1 plus patches to fix various boot failures plus the reversion of
"drm/i915/vlv: re-enable hotplug detect based probing on VLV/BYT" (that's
71977), multiple testers have confirmed you can get KMS to work on Bay Trail
tablets.
On the Venue 8 Pro, the modesetting does not correctly discover the device's
preferred mode, though, which is 800x1280 (the screen's 'native' orientation is
portrait). It decides on 1024x768.
I've captured the EDID of the screen - I'll attach it. The thing that leaps out
to me as being incorrect is that the minimum hsync and vsync are both set to 0,
which is I believe outside the spec (Wikipedia sez it should be in the range of
1–255 kHz).
If I run monitor-parse-edid on the unmodified EDID, it barfs:
[adamw@adam data]$ monitor-parse-edid AUO00C4.bin
bad HorizSync
with a version hex edited to bump the min hsync and vsync to 10 (hex, so
16kHz), it works:
[adamw@adam data]$ monitor-parse-edid AUO00C4_mod.bin
EISA ID: AUO00c4
EDID version: 1.3
EDID extension blocks: 0
Screen size: 10.8 cm x 17.2 cm (8.00 inches, aspect ratio 0.63)
Gamma: 3.55
Digital signal
Max video bandwidth: 80 MHz
HorizSync 16-173
VertRefresh 16-60
# Monitor preferred modeline (60.0 Hz vsync, 78.0 kHz hsync, ratio 0.62,
188 dpi)
ModeLine "800x1280" 76.75 800 824 828 984 1280 1288 1292 1300 -hsync -vsync
I know the kernel code isn't the same as monitor-parse-edid, but it still seems
indicative.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>