From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Joey Lee <jlee@novell.com>
Cc: linux-acpi@vger.kernel.org, Dennis.Jansen@web.de
Subject: Re: [PATCH] Add intel drm blacklist to intel_opregion_present detect
Date: Mon, 12 Jul 2010 03:27:09 +0100 [thread overview]
Message-ID: <20100712022709.GA2695@srcf.ucam.org> (raw)
In-Reply-To: <4C3B06C9020000230001CC2C@novprvlin0050.provo.novell.com>
On Sun, Jul 11, 2010 at 08:12:57PM -0600, Joey Lee wrote:
> He tested the drm blacklist patch can works fine on his computer, it's
> also works on VESA mode because the acpi _BCM, _BQC direct change
> brightness by opregion.
>
> What can we do for this situtation? I mean if the BIOS have opregion
> implementation but there have no opensource drm driver or native video
> driver support opregion on Linux?
The cleanest way would be to implement a stub backlight control driver
for the chip - there should be enough information in the source of the
poulsbo drm to do that. The main problem with the blacklist approach is
that there's no guarantee that all poulsbo systems will have a working
acpi method, and I /think/ there's a couple more PCI IDs that ought to
be covered in any case. On the other hand doing it properly does involve
writing rather a lot more code, and the fact that Intel have shown
absolutely no interest in making their hardware work means that the
quick hack might be the most reasonable thing to do.
--
Matthew Garrett | mjg59@srcf.ucam.org
next parent reply other threads:[~2010-07-12 2:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C3B06C9020000230001CC2C@novprvlin0050.provo.novell.com>
2010-07-12 2:27 ` Matthew Garrett [this message]
2010-08-25 9:52 [PATCH] Add intel drm blacklist to intel_opregion_present detect Joey Lee
-- strict thread matches above, loose matches on Subject: below --
2010-08-24 14:51 Joey Lee
2010-08-24 10:08 Joey Lee
2010-08-24 14:20 ` Matthew Garrett
2010-08-24 14:22 ` Matthew Garrett
2010-08-24 14:51 ` Greg KH
2010-08-24 14:58 ` Matthew Garrett
2010-08-24 21:35 ` Greg KH
2010-08-24 7:03 Joey Lee
2010-08-24 4:53 Joey Lee
2010-08-23 12:43 Joey Lee
2010-08-23 11:40 Lee, Chun-Yi
2010-08-23 11:49 ` Matthew Garrett
2010-08-23 17:53 ` Thomas Renninger
2010-08-23 17:51 ` Matthew Garrett
2010-08-23 14:18 ` Thomas Renninger
2010-07-13 8:13 Joey Lee
2010-07-12 15:12 Joey Lee
2010-07-12 15:19 ` Matthew Garrett
2010-07-11 0:30 Lee, Chun-Yi
2010-07-11 0:29 Lee, Chun-Yi
2010-07-11 14:27 ` Matthew Garrett
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=20100712022709.GA2695@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=Dennis.Jansen@web.de \
--cc=jlee@novell.com \
--cc=linux-acpi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).