From: Alan Jenkins <sourcejedi.lkml-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Chris Bagwell <chris-ZCD0YumhXB+iMFqZbmIluw@public.gmane.org>
Cc: ACPI Devel Maling List
<linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
platform-driver-x86-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: 1005PE's and backlight controls
Date: Wed, 14 Apr 2010 17:23:22 +0100 [thread overview]
Message-ID: <t2i9b2b86521004140923x9c1aaa64p867674329ae158af@mail.gmail.com> (raw)
In-Reply-To: <y2g3b2dfeb01004131934x67e23d80vc73dfd6d5af133fa-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 4/14/10, Chris Bagwell <chris-ZCD0YumhXB+iMFqZbmIluw@public.gmane.org> wrote:
> Hi all,
>
> I've seen the following issue reported on various web pages but not sure if
> it was directly reported. First up, you guys know about issue with acpi_osi
> of "Windows 2009" disables eeepc_backend and thats were eeepc_wmi comes in.
[Subsequent messages from Chris clarified that both eeepc-laptop and
eeepc-wmi suffer as described below]
> There is a secondary bug though if you boot with acpi_osi="!Windows 2009"
> (or "Linux"). The ACPI driver will take control of backlight controls with
> Fn-F5/F6. Those keys will work but has issues with Gnome and other user
> processes.
>
> Anything that uses any of the /sys/* interfaces to control backlight do not
> work correctly. When software cycles threw levels, the behavior is kinda
> odd. It will cycle each time you dim to something like
> Bright->Dim->Bight->Off->Bright->etc. Also, Gnome will give no feedback
> because eeepc_laptop discards the events and it will not make it to
> /dev/input/event*. And last, the status of current brightness is never
> updated under /sys/* correctly which confuses Gnome as well.
>
> The secondary work around is to add acpi_backlight=vendor to boot options.
> Then eepc_backlight takes charge and life is good. Gnome gives visual
> feedback and dimmer works as expected.
>
> Baring a firmware fix from Asus, would it be possible to enable some sort of
> backlist for using ACPI backlight support and have 1005P's use eeepc_laptop?
>
> Chris
I suggest you contact the ACPI video maintainer, Zhang Rui
<rui.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>, and attach the output of "dmidecode". The best
way would probably be to report the problem on bugzilla.kernel.org (on
the ACPI video driver).
I think it will indeed be possible to blacklist your machine, because
someone has already anticipated this problem :-).
drivers/acpi/video_detect.c:
long acpi_video_get_capabilities(acpi_handle graphics_handle)
...
/* Add blacklists here. Be careful to use the right *DMI* bits
* to still be able to override logic via boot params, e.g.:
*
* if (dmi_name_in_vendors("XY")) {
...
* acpi_video_support |=
* ACPI_VIDEO_BACKLIGHT_DMI_VENDOR;
*}
*/
Regards
Alan
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
next parent reply other threads:[~2010-04-14 16:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <y2g3b2dfeb01004131934x67e23d80vc73dfd6d5af133fa@mail.gmail.com>
[not found] ` <y2g3b2dfeb01004131934x67e23d80vc73dfd6d5af133fa-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-14 16:23 ` Alan Jenkins [this message]
2010-04-14 16:40 ` [Acpi4asus-user] 1005PE's and backlight controls Matthew Garrett
2010-04-14 17:14 ` Chris Bagwell
2010-04-14 17:26 ` Matthew Garrett
2010-04-14 22:18 ` Chris Bagwell
2010-04-15 1:30 ` Zhang Rui
2010-04-15 1:42 ` Zhang Rui
2010-04-15 2:10 ` [Acpi4asus-user] " Chris Bagwell
2010-04-15 2:29 ` Zhang Rui
2010-04-16 0:02 ` Chris Bagwell
2010-04-15 2:00 ` Chris Bagwell
2010-04-14 20:07 ` Corentin Chary
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=t2i9b2b86521004140923x9c1aaa64p867674329ae158af@mail.gmail.com \
--to=sourcejedi.lkml-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
--cc=acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=chris-ZCD0YumhXB+iMFqZbmIluw@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=platform-driver-x86-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).