All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Bagwell <chris@cnpbagwell.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: acpi4asus-user@lists.sourceforge.net,
	platform-driver-x86@vger.kernel.org
Subject: Re: [Acpi4asus-user] 1005PE's and backlight controls
Date: Wed, 14 Apr 2010 09:00:16 -0500	[thread overview]
Message-ID: <i2tdb599ead1004140700v22d8e0c2ta01d5d130922a075@mail.gmail.com> (raw)
In-Reply-To: <p2t71cd59b01004140645v587098bdg2fb3628bcf2a78d3@mail.gmail.com>

On Wed, Apr 14, 2010 at 8:45 AM, Corentin Chary
<corentin.chary@gmail.com> wrote:
> On Wed, Apr 14, 2010 at 3:24 PM, Chris Bagwell <chris@cnpbagwell.com> wrote:
>> On Wed, Apr 14, 2010 at 1:16 AM, Corentin Chary
>> <corentin.chary@gmail.com> wrote:
>>> On Wed, Apr 14, 2010 at 4:34 AM, Chris Bagwell <chris@cnpbagwell.com> 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.
>>>>
>>>> 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
>>>
>>> Hi,
>>> Did you try the eeepc-wmi ? It's the long term solution and it don't need
>>> any extra kernel parameters. Yong Wang just added backlight support to it.
>>>
>>> http://git.kernel.org/?p=linux/kernel/git/mjg59/platform-drivers-x86.git;a=shortlog;h=refs/heads/for_linus
>>>
>>
>> I havent't tried it yet but it looks like it has same issue that
>> eeepc-laptop does.  If ACPI reports it handles backlight then
>> eeepc-wmi disables controlling of backlight and I'd get buggy ACPI
>> version.
>>
>> Does Yong happen to be on this email list?
>
> I don't think, but he reads platform-x86 which is now CCed
>
> Are you sure that the backlight behavior is the same with and without
> acpi_osi=Linux ?
>

I just retested to be sure and I think this confirms my suspicion that
using eeepc-wmi will not work either for 1005PE's backlights.

I tried no acpi_osi (same as "WIndows 2009" I guess),
acpi_osi="!Windows 2009", and acpi_osi="Linux"... all without
specifying acpi_backlight=vendor.  They all had the same behaviour.
The later two options allow eeepc-laptop to load and it always gives
message about ACPI controlling backlight.

You can see bad behaviour easiest by using Gnome's Preferences->Power
Management and controlling dimmer.  Sliding between 0% and 100% gives
seemingly random behaviour.  Anything software based acts bad.

Since ACPI did seem to be controlling backlight when I didn't specify
an acpi_osi, I suspect that means eeepc-wmi's logic to disable
backlight support would be invoked for 1005PE's.

Chris
--
To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-04-14 14:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <y2g3b2dfeb01004131934x67e23d80vc73dfd6d5af133fa@mail.gmail.com>
     [not found] ` <o2z71cd59b01004132316jd06b2a40m593ee5376e4dfa28@mail.gmail.com>
     [not found]   ` <r2odb599ead1004140624g56c2465qc4aaa3d1ee1c79b3@mail.gmail.com>
2010-04-14 13:45     ` [Acpi4asus-user] 1005PE's and backlight controls Corentin Chary
2010-04-14 14:00       ` Chris Bagwell [this message]
2010-04-15  3:34         ` Wang, Yong Y
2010-04-15  4:35           ` Wang, Yong Y
     [not found] ` <y2g3b2dfeb01004131934x67e23d80vc73dfd6d5af133fa-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-14 16:23   ` Alan Jenkins
2010-04-14 16:40     ` [Acpi4asus-user] " 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=i2tdb599ead1004140700v22d8e0c2ta01d5d130922a075@mail.gmail.com \
    --to=chris@cnpbagwell.com \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=corentin.chary@gmail.com \
    --cc=platform-driver-x86@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.