<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [HSW]igt/kms_setmode/clone-exclusive-crtc fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68463#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [HSW]igt/kms_setmode/clone-exclusive-crtc fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68463">bug 68463</a>
from <span class="vcard"><a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> <span class="fn">Daniel Vetter</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=68463#c2">comment #2</a>)
<span class="quote">> But at some point we'll start reject mode sets, so we'll also have to fix
> kms_setmode so it can be aware of the case where a mode set fails. A case we
> certainly need to reject: when there are 2 connectors on a single encoder,
> it shouldn't be possible to set modes on both connectors.</span >
If a modeset fails setmode only ensures that errno == EINVAL and not something
else. So I think it shouldn't fail the test if the kernel rejects a modeset.
Once we have atomic modesets we can go more fancy and make sure that every real
modeset works iff the test modeset also checked out.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>