From: Adam Jackson <ajax@redhat.com>
To: Andrew Shadura <bugzilla@tut.by>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/edid: Fix the HDTV hack yet more.
Date: Wed, 22 Feb 2012 17:09:22 -0500 [thread overview]
Message-ID: <1329948562.4548.3.camel@atropine> (raw)
In-Reply-To: <20120222235619.3f6cbe8b@ileemo>
[-- Attachment #1.1: Type: text/plain, Size: 660 bytes --]
On Wed, 2012-02-22 at 23:56 +0300, Andrew Shadura wrote:
> Well, my fault, I haven't read the code 10 lines above :) Indeed, that's
> not STD, it's DTD. And I'm not sure how to fix it then, but DTD gives
> 1360x768, and that isn't quite correct.
Yeah, that's a different class of bug, that's the monitor vendor
refusing to use the precision that the DTD has.
The usual method for fixing that is the quirks table. My concern in
this particular case is whether it's better to just always disbelieve
1360x768 in DTDs or whether we should build up a ton of quirks. I've
tended to side with not second-guessing DTD modes out of caution.
- ajax
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2012-02-22 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 16:08 [PATCH] drm/edid: Fix the HDTV hack yet more Andrew Shadura
2012-02-22 18:05 ` Adam Jackson
2012-02-22 20:56 ` Andrew Shadura
2012-02-22 22:09 ` Adam Jackson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1329948562.4548.3.camel@atropine \
--to=ajax@redhat.com \
--cc=bugzilla@tut.by \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.