mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Azael Avalos <coproscefalo@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org, dsilvers@simtec.co.uk,
	toshiba_acpi@memebeam.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] toshiba-acpi: Support TOS1900-type devices
Date: Tue, 9 Jun 2009 18:29:51 -0600	[thread overview]
Message-ID: <74962ea30906091729i3e445de8i7f45ccfe5e9ea234@mail.gmail.com> (raw)
In-Reply-To: <20090610002236.GA19743@srcf.ucam.org>

On Tue, Jun 9, 2009 at 6:22 PM, Matthew Garrett<mjg59@srcf.ucam.org> wrote:
> On Tue, Jun 09, 2009 at 06:18:59PM -0600, Azael Avalos wrote:
>
>> Indeed an i8042 event pops up, actually dmesg shows the following
>> regardless of the hotkey pressed, even by only pressing the Fn key:
>>
>> atkbd.c: Unknown key released (translated set 2, code 0x6e on isa0060/serio0).
>> atkbd.c: Use 'setkeycodes 6e <keycode>' to make it known.
>
> On press or on release? We could potentially grab that inside
> toshiba_acpi and use that to trigger the poll, but we'd still need to
> clear the value again.

On both actually

> That's kind of ugly. The _Q43 method is clearly
> what should be being executed, so maybe there's another call we can make
> that enables it. I'll dig into your DSDT some more.
>

Cool, hopefully you can find something useful there that I missed,
which by the way, that DSDT is incomplete, I can't compile it w/
Intel's compiler...


Saludos
Azael


-- 
-- El mundo apesta y vosotros apestais tambien --

  reply	other threads:[~2009-06-10  0:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 21:45 [PATCH 1/2] toshiba-acpi: Add support for hotkey notifications Matthew Garrett
2009-03-31 21:47 ` [PATCH 2/2] toshiba-acpi: Support TOS1900-type devices Matthew Garrett
2009-03-31 22:06   ` Azael Avalos
2009-03-31 22:11     ` Matthew Garrett
2009-03-31 22:19       ` Azael Avalos
2009-03-31 23:02         ` Matthew Garrett
2009-04-01 16:50           ` Azael Avalos
2009-04-01 16:53             ` Matthew Garrett
2009-04-01 17:03               ` Azael Avalos
2009-04-01 17:07                 ` Matthew Garrett
2009-04-01 17:13                   ` Azael Avalos
2009-06-02 14:03                     ` Matthew Garrett
2009-06-09 16:42                       ` Azael Avalos
2009-06-09 16:45                         ` Matthew Garrett
2009-06-10  0:18                           ` Azael Avalos
2009-06-10  0:22                             ` Matthew Garrett
2009-06-10  0:29                               ` Azael Avalos [this message]
2009-06-18  0:35                                 ` Azael Avalos
2009-04-08  5:44 ` [PATCH 1/2] toshiba-acpi: Add support for hotkey notifications Len Brown
2009-04-11 19:50 ` Frans Pop
2009-04-13 14:50   ` Matthew Garrett
2009-04-13 19:28     ` Frans Pop
2009-04-13 19:43       ` Matthew Garrett
2009-04-13 20:38         ` Frans Pop
2009-04-13 21:18           ` Matthew Garrett
2009-04-13 21:26             ` Frans Pop
2009-04-13 21:31               ` Matthew Garrett
2009-04-18  4:01 ` Len Brown
2009-04-18  5:47   ` Andrey Borzenkov

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=74962ea30906091729i3e445de8i7f45ccfe5e9ea234@mail.gmail.com \
    --to=coproscefalo@gmail.com \
    --cc=dsilvers@simtec.co.uk \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=toshiba_acpi@memebeam.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

all inboxes | Powered by JetHome®