http://bugs.freedesktop.org/show_bug.cgi?id=16055
--- Comment #12 from Alex Deucher <[EMAIL PROTECTED]> 2008-05-22 19:55:11 PST --- (In reply to comment #11) > Is there any research I can do to help diagnose what needs to be fixed? Some > kind of tracing of the fglrx driver or anything? Or even a particular function > in the driver that I can futz with to see if anything helps? > Well, you can identify the chip by looking at the card. It's probably a siliconimage chip of some sort (sil-something). The hard part is figuring out the gpio line and pins used for i2c to configure the chip. You may be able to tell from tracing what the bios or fglrx does when it sets a mode on that ouput. As to the radeon driver, take a look at RADEONInitExtTMDSInfoFromBIOS() and RADEONGetExtTMDSInfoFromBIOS(). The bios has a table for what gpio reg it uses and the commands to set up the chip, but, I'm not sure how to find out what pins it uses or what's needed to enable them. The problem is I think it tends to vary based on the OEM. I'll ask around AMD and see what I can find out. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati