From: Joel Sass <sass.joel@gmail.com>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH] Disable LVDS output on Clientron E830 Thin Client
Date: Tue, 27 Dec 2011 12:06:38 -0500 [thread overview]
Message-ID: <4EF9FB1E.2060408@gmail.com> (raw)
Dear developers,
I've been directed here by Stephan Graber, and Joseph Salisbury. Stephan
has helped me through my first kernel patch, and I am following along
with the steps he took pertaining to the following bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/544671
I am working on a bug located here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/907055 and have
already submitted a patch. Mr Salisbury recommended I contact the
upstream developers in order to have them work this in to the next
release, so here I am.
I have an Intel Atom thin clients with Intel 945GM video cards
installed. They report an LVDS output as active, even though these thin
clients do not have a monitor attached. This is causing the clients to
boot in dual-head mode, with one monitor missing.
Thanks everyone for your time.
The bug above has the patch listed in there, but I will include it again
below:
--- ./intel_lvds.old 2011-12-20 13:25:49.368291249 -0500
+++ ./intel_lvds.c 2011-12-20 13:26:05.160291248 -0500
@@ -709,6 +709,14 @@
},
{
.callback = intel_no_lvds_dmi_callback,
+ .ident = "Clientron E830",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Clientron"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "E830"),
+ },
+ },
+ {
+ .callback = intel_no_lvds_dmi_callback,
.ident = "Asus EeeBox PC EB1007",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK Computer INC."),
next reply other threads:[~2011-12-27 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 17:06 Joel Sass [this message]
2012-01-04 16:44 ` [PATCH] Disable LVDS output on Clientron E830 Thin Client Adam Jackson
2012-01-10 18:03 ` [PATCH] drm/i915: Add Clientron E830 to the ignore LVDS list Joel Sass
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=4EF9FB1E.2060408@gmail.com \
--to=sass.joel@gmail.com \
--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 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.