<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#c8">Comment # 8</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#c7">comment #7</a>) > As for monitor detection, you need to sort out how the ddc lines are wired > up to the connectors. IIRC, r128 only implemented ddc support for DVI, so > for VGA, you'd need to figure out what ddc line (basically just a gpio pad) > it uses and what bits are used for read and write. It should be pretty > similar to radeon. If you can't figure it out from trial and error, you can > try and snoop what the vbios is doing when you issue a vbe ddc command. If r128 cards use a gpio pad for VGA, doesn't that mean they do implement ddc? I looket at which register is used by radeon. It appears to be RADEON_GPIO_VGA_DDC at offset 0x0060. And this is in a part of the code that specifically refers to r128: <a href="http://cgit.freedesktop.org/~agd5f/xf86-video-ati/tree/src/radeon_bios.c?h=r128-support#n347">http://cgit.freedesktop.org/~agd5f/xf86-video-ati/tree/src/radeon_bios.c?h=r128-support#n347</a> Register 0x0060 is not in r128_reg.h, but if I add it by hand, I see the same behaviour that I saw when it was using 0x0068: X crashes as soon as the driver tries to read or write it. When you wrote the r128-support branch, do you remember if the card you tested was VGA or DVI? Also, if it makes a difference, VGA is the secondary port on my card.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>