From: Danny Baumann <dannybaumann@web.de>
To: David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/1] drm/i915: Allow specifying a minimum brightness level for sysfs control.
Date: Tue, 26 Mar 2013 17:55:53 +0100 [thread overview]
Message-ID: <5151D319.5040104@web.de> (raw)
In-Reply-To: <20130326151313.GU9021@phenom.ffwll.local>
Hi,
> Thus far our assumption always was that the acpi backlight works better
> than the intel native backlight. So everything only uses the intel
> backlight if there's no other backlight driver by default.
>
> So if I should merge this as a general solution for Windows 8 machines not
> working properly, we first need to figure out what windows does on these
> machines and either disable the acpi backlight or adapt it.
I fully agree to that. Making acpi_video control usable is preferable
over using intel_backlight. As I lack the detail knowledge about the
ACPI video stuff, I'd be great of one (or some) of you guys could look
at the mentioned bug report ([1]) and comment on what the problem might
be. I have added the basic needed information already and would be happy
to provide any needed debugging info.
> Adding more kernel options is not a viable solution for the backlight mess
> imo.
Actually I'm fine with hardcoding the percentage as well ;) I just
figured it might make sense to make it controllable for special-case
uses, while still making intel_backlight usable for the 'normal' use case.
Regards,
Danny
[1] https://bugzilla.kernel.org/show_bug.cgi?id=55071
next prev parent reply other threads:[~2013-03-26 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 11:48 [PATCH 0/1] drm/i915: Allow specifying a minimum brightness level for sysfs control Danny Baumann
2013-03-26 11:48 ` [PATCH 1/1] " Danny Baumann
2013-03-26 15:13 ` Daniel Vetter
2013-03-26 15:20 ` Chris Wilson
2013-03-26 17:04 ` Danny Baumann
2013-03-26 16:55 ` Danny Baumann [this message]
2013-03-26 17:02 ` [PATCH 0/1] " Matthew Garrett
2013-03-26 17:10 ` Danny Baumann
2013-03-26 17:21 ` Matthew Garrett
2013-03-27 11:56 ` Danny Baumann
2013-03-27 12:35 ` Alex Deucher
2013-03-27 12:56 ` Danny Baumann
2013-03-27 13:06 ` Alex Deucher
2013-03-27 15:10 ` 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=5151D319.5040104@web.de \
--to=dannybaumann@web.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@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 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.