All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Tygier <samtygier@yahoo.co.uk>
To: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] DRM: ignore invalid EDID extensions
Date: Wed, 22 Sep 2010 22:42:47 +0100	[thread overview]
Message-ID: <4C9A7857.2070004@yahoo.co.uk> (raw)
In-Reply-To: <1285189149.4364.3458.camel@atropine>

On 22/09/10 21:59, Adam Jackson wrote:
> On Tue, 2010-09-21 at 23:02 +0100, Sam Tygier wrote:
>> Currently an invalid EDID extension will cause the whole EDID to be
>> considered invalid. Instead just drop the extension, and return the
>> valid base block. The base block is modified to not claim to have
>> extensions, and update the checksum.
>
> This does not appear to be what your patch does.  I mean, yes, if
> there's only one extension block, that's what it does, but if there's
> more than one...

I could modify it to skip the only invalid extension blocks. As my monitor only claims to have 1 extension block, i could not test this properly. I also spotted that I should make sure that my fix is not run when the base block fails the checksum 4 times. May it should be put within the for loop, replacing "goto carp;".

>> For my EIZO S2242W the base block is fine, but the extension block is
>> all zeros. Without this patch I get no X and no VTs.
>
> I suspect what's actually happening there is that we're failing to get
> the extension block, not that it's being returned as zeros.

Could this be fixed? Anything I could try?

> Also, we shouldn't be converting "checksum failure" to "display
> disconnected".  That's the real bug here.

In my case it would still need to return base block, as that correctly contains all the modes and stuff.

Thanks

Sam

  reply	other threads:[~2010-09-22 21:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 22:02 [PATCH] DRM: ignore invalid EDID extensions Sam Tygier
2010-09-22 20:59 ` Adam Jackson
2010-09-22 21:42   ` Sam Tygier [this message]
2010-09-22 21:55     ` Adam Jackson
2010-09-23 10:05       ` Sam Tygier
2010-10-01 11:15       ` Sam Tygier
  -- strict thread matches above, loose matches on Subject: below --
2010-10-28  9:12 sam tygier
2010-10-28 13:41 ` Marius Gröger

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=4C9A7857.2070004@yahoo.co.uk \
    --to=samtygier@yahoo.co.uk \
    --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 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.