Mailinglist Archive: radeonhd (622 mails)

[Egbert Eich <eich@xxxxxxx>]

Swappp,

this patch is for the ddc test function which will be removed once we
get ddc readout stabilized.
With the support for several outputs setting DPI is actually a problem
as you may have different values per output. 
I think we still need to look into a better solution here.
RandR 1.2 hasn't solved this problem satisfactorily either. Screen
sizes reported by the log file and xdpyinfo may differ and consequently
DPI calculation will be off.

Cheers,
        Egbert.

Swappp writes:
 > This patch help xf86SetDpi access to DDC data. May be not completely correct, in VESA driver for that used vbe module...
 > --- xf86-video-radeonhd-git/src/rhd_driver.c   2007-09-28 20:43:53.000000000 +0400
 > +++ xf86-video-radeonhd/src/rhd_driver.c       2007-09-28 20:46:39.000000000 +0400
 > @@ -1577,7 +1577,7 @@
 >                if (data.monitor) {
 >                    xf86DrvMsg(pScrn->scrnIndex, X_INFO, "Found DDC on line %i:\n",
 >                               i - 1);
 > -                  xf86PrintEDID(data.monitor);
 > +                  pScrn->monitor->DDC = xf86PrintEDID(data.monitor);
 >                } else {
 >                    xf86DrvMsgVerb(pScrn->scrnIndex, 7,X_INFO,
 >                                   "No DDC data found on line %i\n",i - 1);
-- 
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx