From: Chris Wilson <chris@chris-wilson.co.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Knut Petersen <Knut_Petersen@t-online.de>
Cc: airlied@linux.ie, eric@anholt.net, jesse.barnes@intel.com,
linux-kernel@vger.kernel.org,
intel-gfx <intel-gfx@lists.freedesktop.org>,
gregkh@suse.de
Subject: Re: [PATCH] Fix i915 drm regression on AOpen i915GMm-HFS motherboard
Date: Mon, 03 Jan 2011 19:59:34 +0000 [thread overview]
Message-ID: <849307$b0clt4@azsmga001.ch.intel.com> (raw)
In-Reply-To: <AANLkTikffkQJnVKzcGhEZjPqg_iQPQ+P2Bbqz7A9Unq_@mail.gmail.com>
On Mon, 3 Jan 2011 11:45:48 -0800, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Mon, Jan 3, 2011 at 10:12 AM, Knut Petersen
> <Knut_Petersen@t-online.de> wrote:
> >
> > I tried 2.6.37-rc8-git2 with both patches applied.
>
> I thought Chris meant "instead of", rather than "both". Chris?
Right, I was trying to ascertain whether the intel_lvds_ddc_probe()
correctly detected the missing panel. That function currently requires
GMBUS to differentiate between a NAK and an IO error (bitbanging just
returns EREMOTEIO regardless, iirc). So far it has been successful in
detecting one false-positive for an AOpen All-in-one and hasn't fouled
up LVDS detection for the laptops I have.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-03 19:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 14:25 [PATCH] Fix i915 drm regression on AOpen i915GMm-HFS motherboard Knut Petersen
2011-01-03 14:54 ` Chris Wilson
2011-01-03 18:12 ` Knut Petersen
2011-01-03 19:45 ` Linus Torvalds
2011-01-03 19:59 ` Chris Wilson [this message]
2011-01-03 20:26 ` Linus Torvalds
2012-04-04 16:23 ` Jean Delvare
2011-01-03 23:09 ` Knut Petersen
2011-01-03 23:22 ` Chris Wilson
2011-01-04 0:35 ` Knut Petersen
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='849307$b0clt4@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=Knut_Petersen@t-online.de \
--cc=airlied@linux.ie \
--cc=eric@anholt.net \
--cc=gregkh@suse.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jesse.barnes@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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