From: "Tobias Müller" <Tobias_Mueller@twam.info>
To: linux-input@vger.kernel.org
Subject: MacBook keyboard
Date: Mon, 14 Jan 2008 12:39:25 +0100 [thread overview]
Message-ID: <478B49ED.6050505@twam.info> (raw)
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
Hello!
I've got a third-generation MacBook and the Fn-Key is not working,
althought CONFIG_USB_HIDINPUT_POWERBOOK is set to y.
I checked drivers/hid/usbhid/hid-quirks.c and found, that the device_id
of my keyboard isn't specified there.
I changed
#define USB_DEVICE_ID_APPLE_GEYSER4_ISO 0x021b
to
#define USB_DEVICE_ID_APPLE_GEYSER4_ISO 0x022a
and everyhting is working fine.
I had the same issue on my desktop, where I have an new apple desktop
keyboard. Here I had to change to
#define USB_DEVICE_ID_APPLE_GEYSER4_ISO 0x0221
and also everything was working.
Maybe this should be added for the next release.
Regards
Tobias
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3389 bytes --]
reply other threads:[~2008-01-14 11:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=478B49ED.6050505@twam.info \
--to=tobias_mueller@twam.info \
--cc=linux-input@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 NNTP newsgroup(s).