From: Andy Furniss <andyqos@ukfsn.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Joakim Plate <elupus@ecce.se>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm_edid: support CEA video modes
Date: Sat, 19 May 2012 20:44:02 +0100 [thread overview]
Message-ID: <4FB7F802.5040108@ukfsn.org> (raw)
In-Reply-To: <20120519184443.GE4721@phenom.ffwll.local>
Daniel Vetter wrote:
> On Fri, May 18, 2012 at 12:37:51PM +0100, Andy Furniss wrote:
>> Joakim Plate wrote:
>>> Joakim Plate<elupus<at> ecce.se> writes:
>>>
>>>>
>>>> Christian Schmidt<schmidt<at> digadd.de> writes:
>>>>
>>>>>
>>>>> TFT/plasma televisions and projectors have become commonplace, and so
>>>>> has the use of PCs to drive them. Add the video modes specified by an
>>>>> EDID's CEA extension to the mode database for a connector.
>>>>
>>>> /Joakim
>>>>
>>>
>>> Shameless bump on the subject. Would be nice if we could
>>> get this list complete when connecting to HDTV's.
>>
>> Yea, it would be nice.
>>
>> UK bluray seems to use 24/1.001 - not that it's that bad watching
>> with TV@24Hz.
>>
>> I do have issues with interlaced modes on my TV. I don't know how
>> DRM handles interlaced, but CEA says that the number of vblank lines
>> alternates per field. If that isn't happening then I guess that's
>> why.
>
> If this is on an intel gpu, you need kernel 3.4 to make interlaced work.
> If that doesn't help, please file a bug on bugs.freedesktop.org.
> -Daniel
Thanks, but it's AMD I do have a bug open for it.
https://bugs.freedesktop.org/show_bug.cgi?id=35970
Which reminds me - another issue with CEA modes is that the ones that
should be double clocked are not.
prev parent reply other threads:[~2012-05-19 19:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 0:31 [PATCH] drm_edid: support CEA video modes Christian Schmidt
2011-11-13 22:16 ` alanwww1
2011-11-14 18:04 ` Paul Menzel
2011-11-14 22:57 ` Adam Jackson
2011-11-15 0:37 ` alanwww1
2011-11-15 9:37 ` James Cloos
2011-11-20 0:11 ` alanwww1
2011-12-13 17:47 ` Jesse Barnes
2011-12-19 15:02 ` Dave Airlie
2012-02-06 17:41 ` Joakim Plate
2012-05-18 10:11 ` Joakim Plate
2012-05-18 11:37 ` Andy Furniss
2012-05-19 18:44 ` Daniel Vetter
2012-05-19 19:44 ` Andy Furniss [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=4FB7F802.5040108@ukfsn.org \
--to=andyqos@ukfsn.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=elupus@ecce.se \
/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