public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>,
	Zhenyu Wang <zhenyuw@linux.intel.com>,
	Eric Anholt <eric@anholt.net>, mailing54 <mailing54@plzk.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dave Airlie <airlied@redhat.com>,
	dri-devel@lists.sourceforge.net, Ma Ling <ling.ma@intel.com>,
	"Zhao, Yakui" <yakui.zhao@intel.com>
Subject: Re: Linux 2.6.31-rc7
Date: Wed, 26 Aug 2009 10:18:25 -0700	[thread overview]
Message-ID: <20090826101825.455d280e@jbarnes-g45> (raw)
In-Reply-To: <alpine.LFD.2.01.0908260943590.3218@localhost.localdomain>

On Wed, 26 Aug 2009 10:12:14 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> In all three cases the end result is "no EDID", but regardless of
> that, the correct action is basically _never_ to say "ok, I'll just
> assume that the display is on connector XYZ regardless of what the
> state of the graphics chip is".

Yeah, that's normal.  Most builtin panels don't have EDIDs.  Failures
on attached monitors are potentially more serious.

> > so yes I think do better at failing is what is needed, its still
> > failing but its more user friendly fail.
> 
> Yes. If something fails ("oops, I can't seem EDID for any
> connector"), I wish KMS would fail way better than just default to
> some crazy setup. The failure mode should be to at least drive
> whatever the BIOS enabled.

Right, we need to improve our detection heuristics.  We've recently
added some to catch non-existent LVDS displays, but currently don't
have any for VGA.  Using the current configuration as a guide is a
reasonable addition...

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2009-08-26 17:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-22  1:26 Linux 2.6.31-rc7 Linus Torvalds
2009-08-22  3:09 ` Regression: Linux 2.6.31-rc7 lost sensors on asus mobo Gene Heskett
2009-08-22  3:47   ` Linus Torvalds
2009-08-22 12:56     ` Gene Heskett
2009-08-22  6:12   ` Robert Hancock
2009-08-22 10:54     ` Stefan Richter
2009-08-22 13:48       ` Gene Heskett
2009-08-22 14:38         ` Stefan Richter
2009-08-22 19:55           ` Gene Heskett
2009-08-22 13:40     ` Gene Heskett
2009-08-23 10:56 ` Linux 2.6.31-rc7 Geert Uytterhoeven
2009-08-26  5:06   ` KOSAKI Motohiro
2009-08-25 17:25 ` mailing54
2009-08-25 18:11   ` Linus Torvalds
2009-08-25 21:37     ` mailing54
2009-08-25 22:07       ` Linus Torvalds
     [not found]         ` <1251239637.26348.20.camel@gaiman.anholt.net>
2009-08-26  1:51           ` Zhenyu Wang
2009-08-26  3:33             ` Linus Torvalds
2009-08-26  3:47               ` Dave Airlie
2009-08-26  4:13                 ` Linus Torvalds
2009-08-26  4:58                   ` Dave Airlie
2009-08-26 17:12                     ` Linus Torvalds
2009-08-26 17:18                       ` Jesse Barnes [this message]
2009-08-26  6:26                 ` Eric Anholt
2009-08-26  6:35                   ` Dave Airlie
2009-08-26  3:58               ` Zhenyu Wang
2009-08-26  4:20                 ` Linus Torvalds
2009-09-10  5:47                   ` Zhenyu Wang
2009-08-26 10:09                 ` ykzhao
2009-08-30 22:01         ` Tino Keitel

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=20090826101825.455d280e@jbarnes-g45 \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=eric@anholt.net \
    --cc=ling.ma@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailing54@plzk.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yakui.zhao@intel.com \
    --cc=zhenyuw@linux.intel.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