All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Dave Airlie <airlied@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: no LVDS on Intel SandyBridge SDVs
Date: Mon, 20 Dec 2010 18:53:14 -0800	[thread overview]
Message-ID: <20101220185314.7feb7b75@jbarnes-desktop> (raw)
In-Reply-To: <AANLkTikdmUM6W=YHueW05VC_jcfrJeuSYW6-b-_avGeD@mail.gmail.com>

On Tue, 21 Dec 2010 12:43:38 +1000
Dave Airlie <airlied@gmail.com> wrote:

> On Tue, Dec 21, 2010 at 6:05 AM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > Add a DMI match entry for the SDV to indicate it has no LVDS present.
> 
> Sounds wrong, generally the SDVs can get an LVDS panel plugged into
> them, so they have an LVDS connector.

Yeah I think there's actually a header on this board for LVDS so it
would be better to have a way to detect that.  I don't know what that
method would be though...

> I'd worry that this would break something upstream that isn't an SDV.

This DMI info is specific to SandyBridge SDVs, I don't think that part
of the BIOS is used as reference for other vendors.

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2010-12-21  2:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 20:05 [PATCH] drm/i915: no LVDS on Intel SandyBridge SDVs Jesse Barnes
2010-12-20 20:46 ` Chris Wilson
2010-12-21  2:43 ` Dave Airlie
2010-12-21  2:53   ` Jesse Barnes [this message]
2010-12-21 11:36     ` Chris Wilson
2010-12-21 18:14       ` Keith Packard
2010-12-21 19:55         ` Chris Wilson
2010-12-21 20:12           ` Keith Packard
2010-12-22 14:47             ` Chris Wilson

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=20101220185314.7feb7b75@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@gmail.com \
    --cc=intel-gfx@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.