<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [845G regression] on Linux 3.7/3.8: LED monitor "Auto Adjust in Progress" 6-10 seconds at boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=59572#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [845G regression] on Linux 3.7/3.8: LED monitor "Auto Adjust in Progress" 6-10 seconds at boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=59572">bug 59572</a> from <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>(In reply to <a href="show_bug.cgi?id=59572#c2">comment #2</a>) > Hmmm...maybe my questions should include "What happened to 8bpp?" Yeah, I think that's the interesting thing here - the 10s delay for the screen adjusting seems to be annoying, but I don't see anything where the driver blocks for that long. This sometimes also happens in my own test-setups that the screen seems to take awfully long to adjust. For the 8bpp support I've looked through git logs a bit, and it seems that we've parsed this always. So it's more likely that something in the 8bpp support broke (rarely tested unfortunately), and not that it never worked, but for some odd reason we've ignored that on 3.6 kernels. Git bisect of the 8bpp issue would be really interesting ...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>