From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Richard Hughes <hughsient@gmail.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
hal@lists.freedesktop.org
Subject: Re: [PATCH] toshiba_acpi: Add full hotkey support
Date: Sun, 8 Mar 2009 17:29:39 +0300 [thread overview]
Message-ID: <200903081729.49003.arvidjaar@mail.ru> (raw)
In-Reply-To: <15e53e180903080033h5e990f08o3622afae018c38ca@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]
On 8 марта 2009 11:33:48 Richard Hughes wrote:
> On Sat, Mar 7, 2009 at 8:26 PM, Matthew Garrett <mjg59@srcf.ucam.org>
wrote:
> > On Sat, Mar 07, 2009 at 08:19:51PM +0000, Richard Hughes wrote:
> >> Mapping KEY_SUSPEND to hibernate is just insane. Can you please
> >> change the toshiba driver to use KEY_HIBERNATE and KEY_SUSPEND as
> >> thinkpad now does? Thanks.
> >
> > Mapping KEY_SUSPEND to hibernate is what we've been doing for
> > years. It's what hal *still does*.
>
> Sure, but how much userspace now listens to HAL for these events?
Apparently KDE still does. At least it does not seem to pay any
attention to KEY_SUSPEND (nor KEY_SLEEP BTW).
And KDE seems to be important enough customer to not wish to break HAL.
> Xorg and evdev has taken over that role for all the session.
Oh, wait. But even Xorg 1.6.0 interprets KEY_SUSPEND as "hibernate".
KeyPress event, serial 31, synthetic NO, window 0x3e00001,
root 0xbc, subw 0x0, time 87299792, (81,-11), root:(817,290),
state 0x0, keycode 213 (keysym 0x1008ffa8, XF86Hibernate),
same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
So redefining KEY_SUSPEND is going to break Xorg too (as long as anyone
is using those keysyms).
> We can
> ship a trivial patch as an fdi file to HAL to remap this if required.
>
> > KEY_SLEEP has been the suspend to RAM key forever.
Ehh ... actually at least in Toshiba case it was not :) hald Toshiba
add-on always emitted exactly "suspend" and "hibernate" D-Bus events.
Not "sleep".
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-08 14:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 0:39 [PATCH] toshiba_acpi: Add full hotkey support Matthew Garrett
2009-03-06 0:52 ` Matthew Garrett
2009-03-06 9:08 ` Richard Hughes
2009-03-06 9:47 ` Daniel Silverstone
2009-03-06 9:56 ` Matthew Garrett
2009-03-06 10:04 ` Daniel Silverstone
2009-03-06 10:09 ` Matthew Garrett
2009-03-06 10:12 ` Daniel Silverstone
2009-03-06 10:15 ` Matthew Garrett
2009-03-06 10:21 ` Daniel Silverstone
2009-03-06 18:49 ` Andrey Borzenkov
2009-03-06 18:53 ` Matthew Garrett
2009-03-06 18:37 ` Andrey Borzenkov
2009-03-06 18:44 ` Matthew Garrett
2009-03-06 18:57 ` Andrey Borzenkov
2009-03-07 7:27 ` Andrey Borzenkov
2009-03-07 15:06 ` Matthew Garrett
2009-03-07 15:38 ` Andrey Borzenkov
2009-03-07 15:44 ` Matthew Garrett
2009-03-07 20:19 ` Richard Hughes
2009-03-07 20:26 ` Matthew Garrett
2009-03-08 8:33 ` Richard Hughes
2009-03-08 14:29 ` Andrey Borzenkov [this message]
2009-03-08 14:36 ` Matthew Garrett
2009-03-09 17:11 ` Len Brown
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=200903081729.49003.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=hal@lists.freedesktop.org \
--cc=hughsient@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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