<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [r128] Changes needed for RandR support" href="https://bugs.freedesktop.org/show_bug.cgi?id=75629#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [r128] Changes needed for RandR support" href="https://bugs.freedesktop.org/show_bug.cgi?id=75629">bug 75629</a> from <a class="email" href="mailto:connor.behan@gmail.com" title="Connor Behan <connor.behan@gmail.com>"> Connor Behan</a> <pre>(In reply to <a href="show_bug.cgi?id=75629#c23">comment #23</a>) > > Detecting the valid modes with EDID would be nice, but I think this solves > > the most important problem. The driver now knows whether a monitor is > > plugged in and hence whether to drive Crtc2. If you agree, I will send this > > patch to the list. > > Does it actually change when you have a monitor vs. not? If probing works, > you are probably pretty close to getting full i2c working. Yes. And you are right, i2c was almost working. I got it working by trying all 16 combinations for the bits in a loop. The valid pair was (R128_GPIO_MONID_*_3, R128_GPIO_MONID_*_1) instead of (R128_GPIO_MONID_*_3, R128_GPIO_MONID_*_0). Should I just change the *_0 bits to *_1 or should I put that inside a powerpc check? I think the old code might've been for Apple Sense.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>