All of lore.kernel.org
 help / color / mirror / Atom feed
From: Flavio Castelli <flavio-2uVk4PVEUg6lnMjI0IkVqw@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Monitor with corrupted EDID
Date: Fri, 08 Feb 2013 14:11:45 +0100	[thread overview]
Message-ID: <5114F991.3030703@castelli.me> (raw)
In-Reply-To: <5114D712.4060600-H+0wwilmMs3R7s880joybQ@public.gmane.org>

On 02/08/2013 11:44 AM, mwesten wrote:
> My suspicion is that if the EDID data got corrupted in the first place,
> then it's not protected.  I don't know about i2cset, or any other methods.

That's exactly what I'm thinking. I'm trying to overwrite the EEPROM 
using a DVI cable (since it's the DVI EDID which is broken). I saw other 
people used a vga -> dvi cable to do that because some pins could not be 
"exposed" by the DVI cable. I'm don't fully believe in this explanation.

Cheers
Flavio

  parent reply	other threads:[~2013-02-08 13:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 15:16 Monitor with corrupted EDID Flavio Castelli
     [not found] ` <CAAs+i9J0jFhD1==NYEGtwJDUPCH4oaxH7_9rdOsgU-R7iu=Gtg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-07 19:34   ` Marcin Slusarz
2013-02-07 19:37   ` mwesten
     [not found]     ` <51140285.4000108-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2013-02-08  8:23       ` Flavio Castelli
     [not found]         ` <5114B61C.40308-2uVk4PVEUg6lnMjI0IkVqw@public.gmane.org>
2013-02-08 10:44           ` mwesten
     [not found]             ` <5114D712.4060600-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2013-02-08 13:11               ` Flavio Castelli [this message]
     [not found]                 ` <5114F991.3030703-2uVk4PVEUg6lnMjI0IkVqw@public.gmane.org>
2013-02-10 23:33                   ` Dave Airlie

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=5114F991.3030703@castelli.me \
    --to=flavio-2uvk4pveug6lnmji0ikvqw@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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.