All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Meiser <meiser@gmx-topmail.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: platform-driver-x86@vger.kernel.org, Rezwanul_Kabir@dell.com
Subject: Re: Dell Vostro V131: special hotkey not working
Date: Sat, 19 Jan 2013 11:38:56 +0100	[thread overview]
Message-ID: <50FA77C0.4060808@gmx-topmail.de> (raw)
In-Reply-To: <20120425142205.GA14322@srcf.ucam.org>

Hi Matthew,

this topic is still valid. Could you help me debugging the hotkeys?

There're two issues:
1. The "Dell support center" hotkey generates keycode 0xEE, but this is done forever. That means that I don't see a release event.
2. The "Dell instant launch manager" hotkey doesn't generate anything.

Thanks a lot in advance,
Peter

Am 25.04.2012 16:22, schrieb Matthew Garrett:
> On Wed, Apr 25, 2012 at 04:19:51PM +0200, Peter Meiser wrote:
>> Hello Matthew,
>>
>> Am 25.04.2012 15:53, schrieb Matthew Garrett:
>>> watch -n 0.1 cat /proc/interrupts
>>
>> When running "watch -n 0,1 cat /proc/interrupts" (watch -n 0.1 errors out, maybe because of German environment???), the following row increases after each press:
>>
>>   9:          5          0          0          0   IO-APIC-fasteoi   acpi
> 
> Ok, so it's definitely being handled by ACPI somehow - probably via WMI, 
> but unsure. Rez, any chance you can look at the original message and let 
> us know if this is expected to work with the current driver?
> 

  parent reply	other threads:[~2013-01-19 10:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F97FA4C.9040201@gmx-topmail.de>
2012-04-25 13:53 ` Dell Vostro V131: special hotkey not working Matthew Garrett
2012-04-25 14:19   ` Peter Meiser
2012-04-25 14:22     ` Matthew Garrett
2012-05-11  5:28       ` Peter Meiser
2013-01-19 10:38       ` Peter Meiser [this message]
2013-07-20  5:03         ` Peter Meiser
2014-06-12  6:58           ` Peter Meiser

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=50FA77C0.4060808@gmx-topmail.de \
    --to=meiser@gmx-topmail.de \
    --cc=Rezwanul_Kabir@dell.com \
    --cc=mjg59@srcf.ucam.org \
    --cc=platform-driver-x86@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.