Don't log DDC modelines (after hotplug events/xrandr) or "Using XX ranges

from config file" messages. These were printed after hotplug events which
could be frequent in some cases (I have machines where this happens every
10 seconds when the monitor is in a dpms power-saving mode resulting in a
full /var/log filesystem).

EDID vendor/product ID still logged, giving an indication that events are
happening, but reduced from ~3.5KB per event to <100 bytes.

based on a diff from / ok matthieu@
This commit is contained in:
sthen
2024-10-31 11:54:14 +00:00
parent 81fd437204
commit 2be848d404

View File

@@ -1135,8 +1135,10 @@ handle_detailed_monset(struct detailed_monitor_section *det_mon, void *data)
p->Monitor->nHsync++;
}
else {
#ifdef SPAM_XORG_LOG
xf86DrvMsg(scrnIndex, X_INFO,
"Using hsync ranges from config file\n");
#endif
}
if (!p->have_vrefresh) {
@@ -1150,8 +1152,10 @@ handle_detailed_monset(struct detailed_monitor_section *det_mon, void *data)
p->Monitor->nVrefresh++;
}
else {
#ifdef SPAM_XORG_LOG
xf86DrvMsg(scrnIndex, X_INFO,
"Using vrefresh ranges from config file\n");
#endif
}
clock = det_mon->section.ranges.max_clock * 1000;
@@ -1198,6 +1202,7 @@ xf86EdidMonitorSet(int scrnIndex, MonPtr Monitor, xf86MonPtr DDC)
xf86ForEachDetailedBlock(DDC, handle_detailed_monset, &p);
if (Modes) {
#ifdef SPAM_XORG_LOG
/* Print Modes */
xf86DrvMsg(scrnIndex, X_INFO, "Printing DDC gathered Modelines:\n");
@@ -1206,7 +1211,7 @@ xf86EdidMonitorSet(int scrnIndex, MonPtr Monitor, xf86MonPtr DDC)
xf86PrintModeline(scrnIndex, Mode);
Mode = Mode->next;
}
#endif
/* Do we still need ranges to be filled in? */
if (!Monitor->nHsync || !Monitor->nVrefresh)
DDCGuessRangesFromModes(scrnIndex, Monitor, Modes);