From: Dag Bakke <dag@bakke.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Diego 'Flameeyes' Petteno <flameeyes@gmail.com>
Subject: Re: [PATCH] fix apple alu keyboard with numpad
Date: Thu, 08 May 2008 19:24:23 +0200 [thread overview]
Message-ID: <48233747.1030605@bakke.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805062244130.11363@jikos.suse.cz>
Jiri Kosina wrote, On 05/06/2008 10:46 PM:
> On Tue, 6 May 2008, Andrew Morton wrote:
>
>>> The nice apple alu keyboards with numpads are pretty much unusable in
>>> vanilla 2.6.25.
>>> (http://images.apple.com/keyboard/images/gallery/wired_1_20070813.jpg)
>>> Hitting the 'clear' key (=numlock) disables the numpad, and maps multiple
>>> alphanumeric keys to numpad symbols in typical laptopkeyboard fashion.
>> This conflicts rather directly with
>> hid-disable-numlock-emulation-for-apple-aluminium-keyboards.patch below
>> (hm, seems we didn't get a changelog for that one).
>
> Hi,
>
> I have just today applied Diego's patch into my tree [1], he has provided
> the changelog out of list to me.
>
>> Jiri, what should we do here?
>
> Dag, I think Diego's patch should solve the issue you are seeing, right?
>
> [1] http://git.kernel.org/?p=linux/kernel/git/jikos/hid.git;a=commit;h=ffe6f7b799e33f51732520979f9c253a252b9d5e
I'll give it a shot and let you know.
Dag B
next prev parent reply other threads:[~2008-05-08 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 11:19 [PATCH] fix apple alu keyboard with numpad Dag Bakke
2008-05-06 19:54 ` Andrew Morton
2008-05-06 20:46 ` Jiri Kosina
2008-05-08 17:24 ` Dag Bakke [this message]
2008-05-11 22:54 ` Jiri Kosina
2008-05-12 7:45 ` Dag Bakke
2008-05-06 23:43 ` Matthew Garrett
2008-05-08 17:29 ` Dag Bakke
2008-05-08 17:42 ` Matthew Garrett
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=48233747.1030605@bakke.com \
--to=dag@bakke.com \
--cc=akpm@linux-foundation.org \
--cc=flameeyes@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).