From: Michael Buesch <mb@bu3sch.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: Retry i2c transfer of EDID block after failure
Date: Tue, 15 Mar 2011 23:20:31 +0100 [thread overview]
Message-ID: <1300227631.1961.1.camel@marge> (raw)
In-Reply-To: <1300187081-6685-1-git-send-email-chris@chris-wilson.co.uk> (sfid-20110315_120458_565725_FFFFFFFF99171F35)
On Tue, 2011-03-15 at 11:04 +0000, Chris Wilson wrote:
> Usually EDID retrieval is fine. However, sometimes, especially when the
> machine is loaded, it fails, but succeeds after a few retries.
>
> Based on a patch by Michael Buesch.
>
> Reported-by: Michael Buesch <mb@bu3sch.de>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
I'm currently testing this. It boots, but to see if
it fixes the issue, I'll have to run some more tests.
Note that this patch is subject to .37-table
and probably earlier releases, too.
--
Greetings, Michael.
prev parent reply other threads:[~2011-03-15 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 14:56 drm_get_edid i2c failure Michael Buesch
2011-03-15 11:04 ` [PATCH] drm: Retry i2c transfer of EDID block after failure Chris Wilson
2011-03-15 17:02 ` Alex Deucher
2011-03-15 22:20 ` Michael Buesch [this message]
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=1300227631.1961.1.camel@marge \
--to=mb@bu3sch.de \
--cc=chris@chris-wilson.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox