From: Andrew Shadura <bugzilla@tut.by>
To: Adam Jackson <ajax@redhat.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/edid: Fix the HDTV hack yet more.
Date: Wed, 22 Feb 2012 23:56:19 +0300 [thread overview]
Message-ID: <20120222235619.3f6cbe8b@ileemo> (raw)
In-Reply-To: <1329933934.30884.92.camel@atropine>
[-- Attachment #1.1: Type: text/plain, Size: 957 bytes --]
Hello,
On Wed, 22 Feb 2012 13:05:34 -0500
Adam Jackson <ajax@redhat.com> wrote:
> On Wed, 2012-02-22 at 19:08 +0300, Andrew Shadura wrote:
> > Checking for just two variants of standard timings for
> > 1366x768 isn't quite correct, let's check for ranges
> > instead.
> I... doubt it? Standard timing descriptors are a tuple of
> * width in character cells (ie, 8 pixels)
> * one of four aspect ratios
> * refresh rate
> So you're only ever going to have 1360 or 1368, and then in integer
> math I think you could only possibly ever get:
> a) 1360 * 9 / 16 = 765
> b) 1368 * 9 / 16 = 769
> If you're managing to get something else I'm a little concerned, and
> would really be delighted to see the EDID block for it.
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.
--
WBR, Andrew
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 835 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
next prev parent reply other threads:[~2012-02-22 20:56 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 [this message]
2012-02-22 22:09 ` Adam Jackson
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=20120222235619.3f6cbe8b@ileemo \
--to=bugzilla@tut.by \
--cc=ajax@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox