From: Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
zaverel <zaverel-GANU6spQydw@public.gmane.org>
Subject: Re: nouveau Ignoring invalid EDID block 1
Date: Wed, 15 Jun 2011 17:23:19 +0100 [thread overview]
Message-ID: <op.vw4k45cd7cbmmg@emo> (raw)
In-Reply-To: <4DF8D09C.5070704-GANU6spQydw@public.gmane.org>
As you have figured out already the issue is related to the
EDID parser in the common drm code.
I believe somewhere during the development process the parsing
became more strict, thus your issue.
Note the following differences
* "old kernel" - 2.6.36 (modeline via xorg.conf)
1280x720 (0x79) 95.8MHz -HSync +VSync *current +preferred
h: width 1280 start 1360 end 1488 total 1696 skew 0 clock 56.5KHz
v: height 720 start 723 end 728 total 755 clock 74.8Hz
* "new kernel" - 2.6.39 (parsed by drm_edid)
1280x720 (0x79) 74.2MHz +HSync +VSync *current +preferred
h: width 1280 start 1720 end 1760 total 1980 skew 0 clock 37.5KHz
v: height 720 start 725 end 730 total 750 clock 50.0Hz
* parse-edid
Mode "1280x720" # vfreq 50.000Hz, hfreq 37.500kHz
DotClock 74.250000
HTimings 1280 1464 1504 1980
VTimings 720 725 730 750
Flags "+HSync" "+VSync"
EndMode
I would suggest for you to open a bugreport, attaching all the logs,
so that the developers working on the common drm code, can take a
look and provide better/safer solution (if available)
Thanks
next prev parent reply other threads:[~2011-06-15 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 10:24 nouveau Ignoring invalid EDID block 1 zaverel
[not found] ` <4DF88862.9030609-GANU6spQydw@public.gmane.org>
2011-06-15 13:44 ` Emil Velikov
2011-06-15 15:02 ` zaverel
2011-06-15 15:32 ` zaverel
[not found] ` <4DF8D09C.5070704-GANU6spQydw@public.gmane.org>
2011-06-15 16:23 ` Emil Velikov [this message]
2011-06-15 17:08 ` zaverel
[not found] ` <4DF8E70F.1050304-GANU6spQydw@public.gmane.org>
2011-06-16 10:54 ` zaverel
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=op.vw4k45cd7cbmmg@emo \
--to=emil.l.velikov-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=zaverel-GANU6spQydw@public.gmane.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.