From: Nico Schottelius <nico-linux-20111017@schottelius.org>
To: Nico Schottelius <nico-linux-20111017@schottelius.org>,
Jiri Kosina <jkosina@suse.cz>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Keyboard and mouse issues on MacBook Air (4,2)
Date: Wed, 19 Oct 2011 17:01:22 +0200 [thread overview]
Message-ID: <20111019150122.GA6157@schottelius.org> (raw)
In-Reply-To: <20111017214050.GA1408@schottelius.org>
Hey Jiri,
regarding the misplaced keys:
Nico Schottelius [Mon, Oct 17, 2011 at 11:40:50PM +0200]:
> [...]
> I've attached the xev output of fn+{F1-F12}.
>
> F1-F4 are correct, though
> F3 = Expose on MacOS X (**)
> F4 = Dashboard (**)
> F5: not mapped at all: Is KeyboardLightDecrease on MacOSX (*)
> F6 is XF86AudioPrev incorrect: Should be KeyboardLightIncrease (*)
> F7 is XF86AudioPlay incorrect: Should be XF86AudioPrev
> F8 is XF86AudioNext incorrect: Should be XF86AudioPlay
> F9 is XF86AudioMute incorrect: Should be XF86AudioNext
> F10 is XF86AudioLowerVolume incorrect: Should be XF86AudioMute
> F11 is XF86AudioRaiseVolume incorrect: Should be XF86AudioLowerVolume
> F12 is XF86Eject incorrect: Should be XF86AudioRaiseVolume
>
> Thus F7-12 are shifted by one to left in reality and as the MacBook Air
if I want to correct these bugs, which tree should I use as the base?
And when I corrected those, to whom to submit?
I guess the general approach would be to branch out, if it's a mba4,2,
then apply the following mapping, correct?
Cheers,
Nico
--
PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0
next prev parent reply other threads:[~2011-10-19 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 17:59 Keyboard and mouse issues on MacBook Air (4,2) Nico Schottelius
2011-10-17 18:16 ` Jiri Kosina
2011-10-17 21:40 ` Nico Schottelius
2011-10-17 21:49 ` Nico Schottelius
2011-10-19 15:01 ` Nico Schottelius [this message]
2011-10-19 15:04 ` Jiri Kosina
2011-10-19 21:07 ` Nico Schottelius
2011-10-19 21:25 ` Nico Schottelius
2011-10-21 18:22 ` Nico Schottelius
2011-10-22 2:02 ` Nico Schottelius
2011-10-22 10:24 ` Nico Schottelius
2011-10-28 15:46 ` Jiri Kosina
2011-10-31 22:37 ` Nico Schottelius
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=20111019150122.GA6157@schottelius.org \
--to=nico-linux-20111017@schottelius.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@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