X86 platform drivers
 help / color / mirror / Atom feed
From: Mattia Dongili <malattia@linux.it>
To: Stephan Mueller <smueller@chronox.de>
Cc: mjg@redhat.com, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 2.6.35] sony-laptop.c: Adding buttons for Sony Vaio P
Date: Thu, 6 Jan 2011 00:26:47 +0900	[thread overview]
Message-ID: <20110105152612.GA28171@kamineko.org> (raw)
In-Reply-To: <20110105131903.AB5543E65E3@picard.linux.it>

On Wed, Jan 05, 2011 at 02:18:00PM +0100, Stephan Mueller wrote:
> Am Mittwoch, 5. Januar 2011, um 07:13:35 schrieb Mattia Dongili:
> > On Tue, Jan 04, 2011 at 04:40:02PM +0100, Stephan Mueller wrote:
...
> > > - none of the keys mapped to zoom seem to have any effect on my system -
> > > xev does not report the keys when they are pressed - but dmesg does not
> > > list omitted keys either - how are the zoom keys supposed to work?
> > 
> > use /lib/udev/keymap to find out what is being emitted by the kernel
> > (you should know it actually by looking at the number associated to
> > SONYPI_EVENT_ZOOM_PRESSED). If the number is >255 you need remapping
> > that to a lower number, see here for a longer explanation:
> > http://www.linux.it/~malattia/wiki/index.php/Sony-laptop#Fn_keys_in_X
> > If the number is <255 it's just your system is not configured to handle
> > the key.
> 
> Again, before considering that, I think I should see events in xev. As I do 

not really, sony-laptop emits input events via the input layer, Xorg
reads them with the evdev driver and pushes them over to graphical apps.

> not see them, I am scratching my head where the events are lost.

try /lib/udev/keymap, if that sees the events (with your patch applied)
then Xorg is eating your key presses.

> Note, that issue with the zoom keys apply also to the zoom-in and zoom-out 
> keys that are already present in the driver. None of them end up visible in 
> xev. 

Wait, I'm confused. What zoom keys have you got and what should they do?
do you really have zoom-in, zoom-out and a generic zoom?

Thanks
-- 
mattia
:wq!

      parent reply	other threads:[~2011-01-05 15:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110104154024.1DC7C3E65C9@picard.linux.it>
2011-01-04 22:13 ` [PATCH 2.6.35] sony-laptop.c: Adding buttons for Sony Vaio P Mattia Dongili
     [not found]   ` <20110105131903.AB5543E65E3@picard.linux.it>
2011-01-05 15:26     ` Mattia Dongili [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=20110105152612.GA28171@kamineko.org \
    --to=malattia@linux.it \
    --cc=mjg@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=smueller@chronox.de \
    /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