From: Steve White <swhite@zipcon.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Lenovo IdeaPad S206
Date: Sat, 27 Apr 2013 16:15:04 +0000 [thread overview]
Message-ID: <20130427161504.GA8228@iota> (raw)
In-Reply-To: <20130426084624.GA28942@iota>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
Hi,
In the previous post, I had confused the "win" key with the "switch video"
key. This is corrected now. See attached.
I still have several questions:
switch video
------------
The key meant to switch video (mod F10) produces two scan codes.
In man showkey, there are some remarks, but I don't know what they mean.
$ keymap -i /input/event4
scan code: 0xDB
scan code: 0x19
(both scancodes emitted together only once on press,
nothing on longer hold, nothing on release)
$ showkey -s
0x19 on press
0x99 on release
** What does this mean, and how are such results to be used with udev rules?
camera off-on
-------------
I can't see that this key (mod F9) generates anything on any device,
although it does in fact seem to kill the USB-based camera.
** Any ideas?
kill key
----------
The kill key (mod F4) very effectively kills any terminal it's running
in, so I have yet to determine what scan codes it generates.
** Any ideas?
[-- Attachment #2: lenovo-ideapad-s206 --]
[-- Type: text/plain, Size: 683 bytes --]
# key codes on Lenovo IdeaPad S206, and presumably the S200
0x81 reserved # disable lenovo-ideapad mapping
0xB9 reserved # disable lenovo-ideapad mapping
0xBA reserved # disable lenovo-ideapad mapping
0xF1 f6 # mod F6 touchpad toggle (disabled)
0x83 rfkill # mod F7 handled in module-lenovo-ideapad-s206
0xCE micmute # mod F8
#???? camera # mod F9 can't find this in udev
#???? switchvideomode # mod F10 emits multiple scancodes?
0xF0 display_off # mod F11
0xCC brightnessdown # mod F12
0xD4 brightnessup # mod ins
0xDB menu # win key
0x82 unknown # QS key
prev parent reply other threads:[~2013-04-27 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 8:46 Lenovo IdeaPad S206 Steve White
2013-04-27 16:15 ` Steve White [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=20130427161504.GA8228@iota \
--to=swhite@zipcon.net \
--cc=linux-hotplug@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).