drm_mode_detailed() is called quite often, therefore when a monitor
that has a detailed timing mode marked DRM_EDID_PT_STEREO or requiring
composite sync, warning messages will clutter up the kernel log.
Like we already do for incorrect hsync/vsync pluse widths, print these
messages only when KMS d
On Thu, 2013-06-13 at 21:01 +0200, Egbert Eich wrote:
> drm_mode_detailed() is called quite often, therefore when a monitor
> that has a detailed timing mode marked DRM_EDID_PT_STEREO or requiring
> composite sync, warning messages will clutter up the kernel log.
> Like we already do for incorrect
On Thu, 2013-06-13 at 21:01 +0200, Egbert Eich wrote:
> drm_mode_detailed() is called quite often, therefore when a monitor
> that has a detailed timing mode marked DRM_EDID_PT_STEREO or requiring
> composite sync, warning messages will clutter up the kernel log.
> Like we already do for incorrect
drm_mode_detailed() is called quite often, therefore when a monitor
that has a detailed timing mode marked DRM_EDID_PT_STEREO or requiring
composite sync, warning messages will clutter up the kernel log.
Like we already do for incorrect hsync/vsync pluse widths, print these
messages only when KMS d