Dear Alex, yes, the proposed fix should also fix the 'drm/radeon: workaround a hw bug on some radeon chipsets with all-0 EDIDs.' issue. The trick is, that we check within the Radeon domain directly on i2c interface level, if an EDID can be retrieved at all, before we hand over to the main drm edid functions. If you can provide some logs from Dave, I can double-check. Regards, Thomas > On Tue, Jun 21, 2011 at 11:31 AM, Thomas Reim <reimth@xxxxxxxxxxxxxx> wrote: > > Some integrated ATI Radeon chipset implementations > > (e. g. Asus M2A-VM HDMI) indicate the availability > > of a DDC even when there's no monitor connected. > > In this case, drm_get_edid and drm_edid_block_valid > > periodically dump data and kernel errors into system > > log files and onto terminals, which lead to an unacceptable > > system behaviour. > > > > Tested since kernel 2.35 on Asus M2A-VM HDMI board > > > > Signed-off-by: Thomas Reim <rdratlos@xxxxxxxxxxx> > > Does this patch fix the issue: > http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=4a9a8b71e12d41abb71c4e741bff524f016cfef4 > > Alex > > > --- > > drivers/gpu/drm/radeon/radeon_connectors.c | 10 +++++ > > drivers/gpu/drm/radeon/radeon_display.c | 11 +++++ > > drivers/gpu/drm/radeon/radeon_i2c.c | 60 ++++++++++++++++++++++++++++ > > drivers/gpu/drm/radeon/radeon_mode.h | 1 + > > 4 files changed, 82 insertions(+), 0 deletions(-) > > _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
