[PATCH] Fix fn key on Macbook Pro 4,1 and Macbook Air (CC me on replies)

[PATCH] Fix fn key on Macbook Pro 4,1 and Macbook Air (CC me on replies)

[Alexander Karpenko]

Summary: The fn key does not work on Macbook Pro 4,1 and Air,  
preventing the user from using the keyboard's media keys, volume keys,  
PgUp, PgDn, Home, End, Delete, and adjusting screen brightness.

Keywords: macbook, fn key, keyboard, hid, quirks

Kernel version: 2.6.24-16-generic

I've posted the patch to this bug report, which outlines the problem,  
debugging, and fix in more detail: https://bugs.launchpad.net/mactel-support/+bug/207127

The direct link to the patch is: http://launchpadlibrarian.net/14613817/fix_fn_key_on_macbookpro_4_1_and_mb_air.patch

Patch description:
The patch adds the device IDs of the keyboards (ANSI, ISO, JIS for MB  
Pro/Air) to drivers/hid/usbhid/hid-quirks.c.

Please CC me on replies, as I'm not subscribed to this mailing list.

Regards,

Alex

Re: [PATCH] Fix fn key on Macbook Pro 4,1 and Macbook Air (CC me on replies)

[Andrew Morton]

On Sat, 24 May 2008 23:59:01 -0400 Alexander Karpenko <alexander@comm.utoronto.ca> wrote:

> Summary: The fn key does not work on Macbook Pro 4,1 and Air,  
> preventing the user from using the keyboard's media keys, volume keys,  
> PgUp, PgDn, Home, End, Delete, and adjusting screen brightness.
> 
> Keywords: macbook, fn key, keyboard, hid, quirks
> 
> Kernel version: 2.6.24-16-generic
> 
> I've posted the patch to this bug report, which outlines the problem,  
> debugging, and fix in more detail: https://bugs.launchpad.net/mactel-support/+bug/207127
> 
> The direct link to the patch is: http://launchpadlibrarian.net/14613817/fix_fn_key_on_macbookpro_4_1_and_mb_air.patch
> 
> Patch description:
> The patch adds the device IDs of the keyboards (ANSI, ISO, JIS for MB  
> Pro/Air) to drivers/hid/usbhid/hid-quirks.c.
> 
> Please CC me on replies, as I'm not subscribed to this mailing list.
> 

Please include the patch, all relevant descriptive matter and a
signed-off-by: all in the same email.

Documentation/SubmittingPatches goes into details.

Thanks.