mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Norbert Preining <preining@logic.at>
Cc: Mattia Dongili <malattia@linux.it>,
	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: Tue, 16 Nov 2010 23:12:07 -0800	[thread overview]
Message-ID: <20101117071207.GB7046@core.coreip.homeip.net> (raw)
In-Reply-To: <20101117063006.GF29129@gamma.logic.tuwien.ac.at>

On Wed, Nov 17, 2010 at 03:30:06PM +0900, Norbert Preining wrote:
> Hi Mattia, hi Dmitry,
> 
> On Fr, 12 Nov 2010, Mattia Dongili wrote:
> > 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:
> 
> Ok, I have now done the fllowing:
> - recompiled a input-kbd binary with a relaxed version check
> 	-	if (EV_VERSION != version) {
> 	+	if (EV_VERSION > version) {
>   in input.c, line 104 of input-utils.
> 
> - created a vaio-kbd from the output of input-kbd and changed the
>   keys that hat keycode 470 and 471 (those shown in evtest 8)
>   to key_brightness:
> 
> $ diff -u <(./input-kbd 8) vaio-kbd
> --- /dev/fd/63	2010-11-17 15:24:32.023696588 +0900
> +++ vaio-kbd	2010-11-17 15:24:02.000000000 +0900
> @@ -13,8 +13,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
> $
> 
> remember:
> evtest /dev/input/event8 reports code 470 and code 471 for the respective
> Fn-F5 and Fn-F6 combinations.
> 
> > output to a file, edit it to change the keys you need remapped and run
> > `input-kbd -f <file> <devNo>`.
> 
> Then I run
> 	$ ./input-kbd -f vaio-kbd 8
> 	/dev/input/event8
> 	map: 44 keys, size: 59/64
> 	parse error: /dev/input/event8

"Parse error" suggests issue with teh keymap file.

> 	$
> with the effect that still brigthness is not working.
> 
> If someone can explain what is wrong here and how to get this fixed
> that would be nice, because up to now on the sony-vaio mailing list
> I heard many complains about disappearing brightness, I hope we can
> fix that.
> 

I did compile input-utils from sid and after fixing up the version issue
I can change mappings on my AT keyboard. Could you try doing the same -
maybe the issue is with the sony-laptop driver (rather its irectaion
with the large scancode support) as well as with input-kbd utility.

Thanks.

-- 
Dmitry

  parent reply	other threads:[~2010-11-17  7:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 14:29 Norbert Preining
2010-11-10  3:58 ` 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
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 [this message]
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=20101117071207.GB7046@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malattia@linux.it \
    --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

all inboxes | Powered by JetHome®