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: Sat, 22 Oct 2011 12:24:27 +0200 [thread overview]
Message-ID: <20111022102427.GB26724@schottelius.org> (raw)
In-Reply-To: <20111022020205.GA26724@schottelius.org>
I'm making progress in this issue:
I've just grabbed the whole list of manuals for all MacBook Airs from the Apple page
and had a look at the keyboard layout in the manual:
air 2008: new
13" air late 2010: old
11" air late 2010: old
11" air mid 2011: new
13" air mid 2011: new
table_new = with keyboard backlight keys, f5 mapped to backlight down -> apple_fn_keys
table_old = f5 has no fn-special meaning -> macbookair_fn_keys
Reviewing drivers/hid/hid-apple.c you were absolutely right, the
apple_fn_keys[] maps correctly.
The missing bit to correct my previous patch: To which device IDs do the devices
named above match to? I.e. is USB_DEVICE_ID_APPLE_WELLSPRING6_* the
MacBook Air 4,2?
Cheers,
Nico
p.s.: sorry for the noise, was a bit confused.
--
PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0
next prev parent reply other threads:[~2011-10-22 10:24 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
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 [this message]
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=20111022102427.GB26724@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 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.