From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Adrian Bunk <bunk@stusta.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
len.brown@intel.com, linux-acpi@vger.kernel.org,
linux-pm@osdl.org
Subject: Re: x60 backlight Re: [discuss] 2.6.19-rc1: known regressions (v2)
Date: Sun, 08 Oct 2006 16:44:37 -0700 [thread overview]
Message-ID: <45298D65.8090503@goop.org> (raw)
In-Reply-To: <20061008071254.GA5672@ucw.cz>
Pavel Machek wrote:
> Strange, problem went away after reboot. I guess I'll write it off as
> an acpi glitch... there's definitely something strange going on with
> backlight around s2ram: during normal operation, backlight changes are
> fast. After s2ram, backlight change from keyboard takes 300msec or so.
>
Yes, I'm seeing that too. It's not just keyboard brightness changes;
gnome does some fadeup effect, which takes ~300ms/step as well.
J
next prev parent reply other threads:[~2006-10-08 23:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0610042017340.3952@g5.osdl.org>
[not found] ` <871wpmoyjv.fsf@sycorax.lbl.gov>
2006-10-06 18:47 ` 2.6.19-rc1 regression: airo suspend fails Adrian Bunk
2006-10-07 3:54 ` Alex Romosan
2006-10-07 19:52 ` Dave Kleikamp
2006-10-07 20:17 ` Alex Romosan
2006-10-08 6:43 ` Pavel Machek
2006-10-07 21:46 ` 2.6.19-rc1: known regressions (v2) Adrian Bunk
2006-10-08 7:12 ` x60 backlight Re: [discuss] " Pavel Machek
2006-10-08 17:38 ` Adrian Bunk
2006-10-08 17:59 ` Michael S. Tsirkin
2006-10-08 19:30 ` Adrian Bunk
2006-10-16 19:39 ` Michael S. Tsirkin
2006-10-08 18:36 ` Pavel Machek
2006-10-08 19:29 ` Adrian Bunk
2006-10-08 23:44 ` Jeremy Fitzhardinge [this message]
2006-10-08 8:56 ` matthieu castet
2006-10-10 5:10 ` 2.6.19-rc1: known regressions (v3) Adrian Bunk
2006-10-10 22:58 ` Paul Mackerras
2006-10-11 3:08 ` Adrian Bunk
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=45298D65.8090503@goop.org \
--to=jeremy@goop.org \
--cc=bunk@stusta.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=pavel@suse.cz \
/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