From: Eric Anholt <eric@anholt.net>
To: Jarod Wilson <jarod@redhat.com>
Cc: dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
xorg-devel@lists.x.org, notting@redhat.com
Subject: Re: [PATCH resend] drm: ignore LVDS on intel graphics systems that lie about having it
Date: Thu, 14 May 2009 14:16:48 -0700 [thread overview]
Message-ID: <1242335808.9887.61.camel@gaiman.anholt.net> (raw)
In-Reply-To: <200905051000.26701.jarod@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On Tue, 2009-05-05 at 10:00 -0400, Jarod Wilson wrote:
> There are a number of small form factor desktop systems with Intel mobile
> graphics chips that lie and say they have an LVDS. With kernel mode-setting,
> this becomes a problem, and makes native resolution boot go haywire -- for
> example, my Dell Studio Hybrid, hooked to a 1920x1080 display claims to
> have a 1024x768 LVDS, and the resulting graphical boot on the 1920x1080
> display uses only the top left 1024x768, and auto-configured X will end
> up only 1024x768 as well. With this change, graphical boot and X
> both do 1920x1080 as expected.
>
> Note that we're simply embracing and extending the early bail-out code
> in place for the Mac Mini here. The xorg intel driver uses pci subsystem
> device and vendor id for matching, while we're using dmi lookups here.
> The MSI addition is courtesy of and tested by Bill Nottingham.
>
> Signed-off-by: Jarod Wilson <jarod@redhat.com>
> Tested-by: Bill Nottingham <notting@redhat.com>
Looks good, I'm pulling it for 2.6.30. Thanks!
--
Eric Anholt
eric@anholt.net eric.anholt@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-05-14 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 14:00 Jarod Wilson
2009-05-14 21:16 ` Eric Anholt [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=1242335808.9887.61.camel@gaiman.anholt.net \
--to=eric@anholt.net \
--cc=dri-devel@lists.sourceforge.net \
--cc=jarod@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=notting@redhat.com \
--cc=xorg-devel@lists.x.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
all inboxes | Powered by JetHome®