dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lisandro Damián Nicanor Pérez Meyer" <perezmeyer@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Thibaut Girka <thib@sitedethib.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	622993@bugs.debian.org, dri-devel@lists.freedesktop.org,
	Stuart Pook <slp12227@pook.it>
Subject: Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."
Date: Mon, 2 May 2011 13:56:12 -0300	[thread overview]
Message-ID: <201105021356.19085.perezmeyer@gmail.com> (raw)
In-Reply-To: <BANLkTimYhhC20zqxxdJaEi+w1URfat-V3A@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1105 bytes --]

On Monday 02 May 2011 12:25:07 Alex Deucher wrote:
[snip] 
> Can you bisect?  

I really don't know :-) Haven't done it before. On the other hand, I will 
surely not have time to do it until next sunday (if I have time next sunday). 
Sucks, yeah :-/

> I suspect the culprit is one of the patches that made
> the kernel edid parser more strict.  Alternatively, you may have been
> using ums previously which does not have the same strict checks as the
> kernel.

One simple question: is it possible to get the edid info provided by the VGA 
port? In that way one could compare both raw outputs.

-- 
FAQ del pequeño tomi:
P- ¿Porque los programas necesitan tanta RAM hoy?
R- Porque los que programamos somos todos unos subnormales que no
sabemos optimizar nada y nos gusta tener todo en RAM y hacer mmap
a cualquier archivo que queramos acceder en vez de hacerlo como
dios manda (mmap: funcion que mapea un archivo en memoria, no
usar)
  Textual de Martín "El Ruso" Ribelotta

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-05-02 16:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201104292156.32388.perezmeyer@gmail.com>
     [not found] ` <20110430010752.GA6907@elie>
     [not found]   ` <201104292359.45739.perezmeyer@gmail.com>
2011-04-30  4:11     ` every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..." Jonathan Nieder
2011-05-01 15:26       ` Bug#622993: " Stuart Pook
2011-05-01 19:40         ` Thibaut Girka
2011-05-01 19:51           ` Lisandro Damián Nicanor Pérez Meyer
2011-05-01 20:26             ` Thibaut Girka
2011-05-01 20:47               ` Lisandro Damián Nicanor Pérez Meyer
2011-05-01 21:09                 ` Thibaut Girka
2011-05-01 21:31                   ` Lisandro Damián Nicanor Pérez Meyer
2011-05-02 14:23                     ` Alex Deucher
2011-05-02 14:50                       ` Lisandro Damián Nicanor Pérez Meyer
2011-05-02 15:25                         ` Alex Deucher
2011-05-02 16:56                           ` Lisandro Damián Nicanor Pérez Meyer [this message]
2011-05-01 20:48               ` Stuart Pook
2014-02-17  3:39         ` Lisandro Damián Nicanor Pérez Meyer

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=201105021356.19085.perezmeyer@gmail.com \
    --to=perezmeyer@gmail.com \
    --cc=622993@bugs.debian.org \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jrnieder@gmail.com \
    --cc=slp12227@pook.it \
    --cc=thib@sitedethib.com \
    /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