From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Jackson Subject: Re: [PATCH] drm: don't add inferred modes for monitors that don't support them Date: Fri, 15 Feb 2013 12:27:54 -0500 Message-ID: <1360949274.18532.26.camel@ergine> References: <1360942587-3621-1-git-send-email-przanoni@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1360942587-3621-1-git-send-email-przanoni@gmail.com> Sender: stable-owner@vger.kernel.org To: Paulo Zanoni Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org, Paulo Zanoni , stable@vger.kernel.org List-Id: intel-gfx@lists.freedesktop.org On Fri, 2013-02-15 at 13:36 -0200, Paulo Zanoni wrote: > From: Paulo Zanoni > > If bit 0 of the features byte (0x18) is set to 0, then, according to > the EDID spec, "the display is non-continuous frequency (multi-mode) > and is only specified to accept the video timing formats that are > listed in Base EDID and certain Extension Blocks". > > For more information, please see the EDID spec, check the notes of the > table that explains the "Feature Support" byte (18h) and also the > notes on the tables of the section that explains "Display Range Limits > & Additional Timing Description Definition (tag #FDh)". Seems sane. Reviewed-by: Adam Jackson - ajax