[Bug 75629] [r128] Changes needed for RandR support

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=75629

--- Comment #13 from Alex Deucher <agd5f at yahoo.com> ---
(In reply to comment #8)
> (In reply to comment #7)
> > 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:
> http://cgit.freedesktop.org/~agd5f/xf86-video-ati/tree/src/radeon_bios.
> c?h=r128-support#n347
> 
> 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.

I think my code is wrong.  You should probably use R128_GPIO_MONID (0x68) or
R128_GPIO_MONIDB (0x6c) rather than RADEON_GPIO_DVI_DDC or RADEON_GPIO_VGA_DDC.
and use the R128_GPIO_MONID_*_3 and R128_GPIO_MONID_*_0 bits rather the bits
used on radeon.  Basically just follow the logic in the existing R128I2c*()
functions.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-driver-ati/attachments/20140516/7914d2b3/attachment.html>