From: Andrew Barr <barr.156-ZbGKxL/pcrQ@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH 2/2] Video Extension patch
Date: Thu, 26 Aug 2004 17:30:02 -0400 [thread overview]
Message-ID: <1093555801.11567.26.camel@6-allhosts> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84054F41D0@pdsmsx403>
On Thu, 2004-08-26 at 06:21, Yu, Luming wrote:
> All,
> Since Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> has implemented acpi video
> extension filed at bug 1944.
> I made some improvement against his code.
>
> The patch [1/2] posted here is the original implementation of video
> extension written by Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> .
> The patch [2/2] posted here is my patch on top of the patch [1/2].
> Please give it a review, and have it a try.
>
> Thanks
> Luming
Hello,
I have a Dell Insprion 300m notebook with an Intel 855GM integrated
graphics device. I gave the video extensions code a try, primarily with
an interest in brightness control from userspace (for example, lowering
brightness at a certain battery level). Right now, the brightness keys
(Fn+Up/Down Arrow) are caught by the BIOS and work without any extra
code in the kernel. There are two problems for me right now: first,
brightness control is not effective. Doing:
root@dell-laptop /home/abarr/tmp # echo 40 >
/proc/acpi/video/GFX0/LCD/brightness
root@dell-laptop /home/abarr/tmp # cat
/proc/acpi/video/GFX0/LCD/brightness
levels: 80 60 0 20 40 60 80 100
current: 40
will change the current value, as you can see, but it does not change
the brightness value for my screen. Second, pressing the brightness
control buttons with the video extensions patch applied causes a loss of
keyboard input. The mouse will work, but both internal and external
keyboards are dead after using those keys. BIOS-trapped keys such as
brightness and CRT/LCD still work. I do get a video event in
/proc/acpi/event when I press the CRT/LCD switch key.
Now, I realize that this code is new and experimental. I'm just hacking
around here, and if anyone gets a chance to help me out I'd greatly
appreciate it.
Andrew
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next prev parent reply other threads:[~2004-08-26 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 10:21 [PATCH 2/2] Video Extension patch Yu, Luming
2004-08-26 21:30 ` Andrew Barr [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-01 11:29 Yu, Luming
2004-09-02 6:10 Yu, Luming
2004-09-02 18:07 ` Andrew Barr
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=1093555801.11567.26.camel@6-allhosts \
--to=barr.156-zbgkxl/pcrq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@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