dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27708] [KMS] Repeated EDID errors despite everything working
Date: Wed,  5 Jan 2011 15:52:00 -0800 (PST)	[thread overview]
Message-ID: <20110105235200.3B11713004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-27708-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=27708

--- Comment #8 from Sergej Pupykin <ps@lx-ltd.ru> 2011-01-05 15:52:00 PST ---
(In reply to comment #7)
> The drm EDID checker is pretty strict about what EDIDs it will accept.  Try
> this patch and add drm.edid_strict=0 to your kernel command line.

It stops spamming with drm.edid_strict=0 (2.6.37+this patch)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-01-05 23:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16 22:16 [Bug 27708] New: [KMS] Repeated EDID errors despite everything working bugzilla-daemon
2010-04-16 22:16 ` [Bug 27708] " bugzilla-daemon
2010-04-16 22:16 ` bugzilla-daemon
2010-04-16 22:17 ` bugzilla-daemon
2010-04-16 22:18 ` bugzilla-daemon
2010-04-16 22:22 ` bugzilla-daemon
2011-01-01 13:03 ` bugzilla-daemon
2011-01-01 13:07 ` bugzilla-daemon
2011-01-04 23:04 ` bugzilla-daemon
2011-01-05 23:52 ` bugzilla-daemon [this message]
2011-01-12 20:57 ` bugzilla-daemon
2011-01-25 16:59 ` bugzilla-daemon
2011-01-25 17:33 ` bugzilla-daemon
2011-02-18 18:28 ` bugzilla-daemon
2011-02-18 18:41 ` bugzilla-daemon
2011-02-18 18:44 ` bugzilla-daemon
2011-02-18 19:05 ` bugzilla-daemon
2011-02-18 21:32 ` bugzilla-daemon
2012-10-23 21:40 ` bugzilla-daemon
2012-10-24 16:34 ` bugzilla-daemon

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=20110105235200.3B11713004E@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --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;
as well as URLs for NNTP newsgroup(s).