From: Mattia Dongili <malattia@linux.it>
To: Norbert Preining <preining@logic.at>
Cc: Matthew Garrett <mjg@redhat.com>,
linux-kernel@vger.kernel.org,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: regression since 2.6.36: backlight in sony-laptop not working
Date: Fri, 12 Nov 2010 13:22:43 +0900 [thread overview]
Message-ID: <20101112042243.GE2852@kamineko.org> (raw)
In-Reply-To: <20101112035732.GB7574@srcf.ucam.org>
On Fri, Nov 12, 2010 at 03:57:32AM +0000, Matthew Garrett wrote:
> On Fri, Nov 12, 2010 at 12:50:27PM +0900, Norbert Preining wrote:
> > THen the problem is simply that the acpi events are not coming through
> > when pressing the respective keys.
>
> Then yes, that's probably related to sony-laptop. If you run evtest
> against the /dev/input/event device that corresponds to sony-laptop,
> what events do you get when you hit the brightness keys?
backlight (actually Fn+F[56]) is one of those keys the needs remapping
these days, i.e. if xev doesn't get any event in X then you may need
something like:
$ diff -u <(sudo input-kbd 5) vaio-kbd
/dev/input/event5
bustype : BUS_ISA
vendor : 0x104d
product : 0x0
version : 0
name : "Sony Vaio Keys"
bits ev : EV_SYN EV_KEY EV_MSC
map: 44 keys, size: 59/64
--- /proc/self/fd/11 2010-11-12 13:10:39.811178332 +0900
+++ vaio-kbd 2010-10-31 19:24:49.000000000 +0900
@@ -4,8 +4,8 @@
0x0006 = 467 # KEY_FN_F2
0x0007 = 468 # KEY_FN_F3
0x0008 = 469 # KEY_FN_F4
-0x0009 = 470 # KEY_FN_F5
-0x000a = 471 # KEY_FN_F6
+0x0009 = 224 # KEY_BRIGHTNESSDOWN
+0x000a = 225 # KEY_BRIGHTNESSUP
0x000b = 472 # KEY_FN_F7
0x000c = 473 # KEY_FN_F8
0x000d = 474 # KEY_FN_F9
See the manpage for input-kbd and /usr/include/linux/input.h for valid
key values.
In short `input-kbd <devNo>` gives you the current map. Redirect the
output to a file, edit it to change the keys you need remapped and run
`input-kbd -f <file> <devNo>`.
For a reference look at this bug report:
http://bugs.freedesktop.org/show_bug.cgi?id=11227
If the above is not the case then there might be another problem in
sony-laptop as Matthew suggests.
--
mattia
:wq!
next prev parent reply other threads:[~2010-11-12 4:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101104142915.GC7650@gamma.logic.tuwien.ac.at>
2010-11-10 3:58 ` regression since 2.6.36: backlight in sony-laptop not working Mattia Dongili
2010-11-11 23:50 ` Norbert Preining
2010-11-12 3:44 ` Matthew Garrett
2010-11-12 3:50 ` Norbert Preining
2010-11-12 3:57 ` Matthew Garrett
2010-11-12 4:14 ` Norbert Preining
2010-11-12 4:22 ` Mattia Dongili [this message]
2010-11-12 4:39 ` Norbert Preining
2010-11-12 12:17 ` Mattia Dongili
2010-11-16 5:16 ` Norbert Preining
2010-11-16 14:18 ` Mattia Dongili
2010-11-16 17:41 ` Dmitry Torokhov
2010-11-17 6:30 ` Norbert Preining
2010-11-17 6:33 ` Norbert Preining
2010-11-17 6:52 ` Dmitry Torokhov
2010-11-18 11:04 ` Mattia Dongili
2010-11-18 13:34 ` Mattia Dongili
2010-11-18 18:06 ` Dmitry Torokhov
2010-11-17 7:12 ` Dmitry Torokhov
2010-11-12 7:38 ` Zhang Rui
2010-11-12 10:10 ` Norbert Preining
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=20101112042243.GE2852@kamineko.org \
--to=malattia@linux.it \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=preining@logic.at \
/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