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

[bugzilla-daemon at freedesktop.org]

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

--- Comment #22 from Alex Deucher <agd5f at yahoo.com> ---
(In reply to comment #20)
> (In reply to comment #13)
> > 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.
> 
> The most recent patch tries calling xf86DoEDID_DDC2() for all types of cards
> with the existing I2c logic. This no longer crashes but it still fails to
> detect the VGA monitor. xf86DoEDID_DDC2() returns NULL no matter what so
> I'll have to do some experimentation. I have three questions about snooping
> the vbe ddc commands.
> 
> 1. By this, do you mean vbeDoEDID()?

Matthew Garret had a hacked up version of vbetool that would trace mmio using
libx86 when executing so you could see what registers were being used.  You
could probably hack vbeDoEDID() and libx86 used by the xserver to do something
similar.

> 
> 2. This detects the monitor perfectly on my card, so why can't the driver
> just use this instead of implementing the I2c stuff? Is it because
> xf86DoEDID_DDC2() is platform independent but vbeDoEDID() is x86 only?

vbeDoEDID() uses vbe which may be problematic on non-x86 platforms and it has
no concept of multiple monitors so if you have a card with more than one
display attached, it's not clear which EDID would be returned.  For R128, it
may be fine since I think most (all?) dualhead capable cards were laptops so
the other display was an LVDS panel and you could get the panel info from the
vbios.

> 
> 3. To snoop what the vbios is doing, would this consist of dumping the
> contents of suspicious registers before and after vbeDoEDID() to see what
> changed? Or should I try to dump the contents *during* that function (i.e.
> patching the vbe module or running radeonreg in a loop)?

You just execute the vbe edid fetch function using vbetool and it would dump
the mmio commands to file which you could then look through to see what was
happening.

-- 
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/20140527/3d17fde5/attachment.html>