<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - Need one kernel option to enable all connected displays" href="https://bugs.freedesktop.org/show_bug.cgi?id=75552#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - Need one kernel option to enable all connected displays" href="https://bugs.freedesktop.org/show_bug.cgi?id=75552">bug 75552</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to <a href="show_bug.cgi?id=75552#c4">comment #4</a>) > (In reply to <a href="show_bug.cgi?id=75552#c3">comment #3</a>) > > i915.fastboot=-1? > > It's a different issue, disabling fastboot just kills the modeset hacks, not > the initial config takeover. I guess we need to be a notch more clever and > also light up any displays not lit up by the bios (but otherwise keep the > crtc/output/modes as set). Assigning to Jesse to polish this more. What I meant is that this QA mode is the antithesis of fastboot - and I want to avoid the mistake of them declaring fastboot a failure because of their own requirements.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>