From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net, Andrew Morton <akpm@osdl.org>
Cc: klug@blarg.org
Subject: Re: Fw: [Bugme-new] [Bug 4468] New: Upgrade to 2.6.11.6 results in no longer being able to turn the lcd backlight off.
Date: Thu, 14 Apr 2005 13:51:25 +0800 [thread overview]
Message-ID: <200504141351.25084.adaplas@hotpop.com> (raw)
In-Reply-To: <20050410172843.6366ef8a.akpm@osdl.org>
On Monday 11 April 2005 08:28, Andrew Morton wrote:
> Previous to my 2.6.11.6 upgrade I was running 2.6.9. With all unpatched 2.6
> kernel versions up to and including 2.6.9, I could turn the lcd backlight
> off by running "echo lcd_out:0 > /proc/acpi/toshiba/video" as root. I
> upgraded directly from 2.6.9 to 2.6.11.6. With the upgrade I am no longer
> able to turn the lcd backlight off. There is no effect after running "echo
> lcd_out:0 >
> /proc/acpi/toshiba/video" and the /proc/acpi/toshiba/video lcd_out option
Looks more like an acpi problem than fbdev/backlight.
> remains unchanged as 1. I recompiled the 2.6.11.6 kernel with the new
> option CONFIG_BACKLIGHT_LCD_SUPPORT=y. Enabling this option did not allow
Does not matter as intelfb does not use the backlight/lcd architecture yet.
Tony
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-04-14 5:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 0:28 Fw: [Bugme-new] [Bug 4468] New: Upgrade to 2.6.11.6 results in no longer being able to turn the lcd backlight off Andrew Morton
2005-04-11 19:10 ` klug
2005-04-12 15:41 ` klug
2005-04-13 4:52 ` klug
2005-04-14 2:54 ` klug
2005-04-14 5:51 ` Antonino A. Daplas [this message]
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=200504141351.25084.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=akpm@osdl.org \
--cc=klug@blarg.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).