From: "Michel Dänzer" <michel@daenzer.net>
To: Matthias Grimm <joker@cymes.de>
Cc: LinuxPPC-Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Why is the Powerbook Fn-Key handled differently?
Date: 05 Feb 2002 11:03:43 +0100 [thread overview]
Message-ID: <1012903423.1594.533.camel@pismo> (raw)
In-Reply-To: <3C5ED0F9.5060908@cymes.de>
On Mon, 2002-02-04 at 19:20, Matthias Grimm wrote:
> I own an Powerbook G3 which has a Fn-Key for his special functions.
> During my kernel source studies I learned that there are two keyboard
> drivers: 1. The old machintosh keyboard driver and
> 2. The new event driven Human Input Device from Vojtech Pavlik
>
> The old driver map the scancode for the Fn-Key to a different value and
> passes it to the Kernel keyboard driver. The new HID filters the Fn-Key
> completely out, as the attached code fragments below show.
>
> Is there any reason to cut out the Fn-Key in the new input driver?
> Nevertheless the Fn-Key is hard wired with the special keys and the
> number block, it would helpful to have an additional qualifier key on
> this small keyboard.
If the fn key generates a keycode, existing shortcuts involving it won't
work anymore, will they? I'm specifically thinking of stuff like
ctrl-alt-{+,-} to switch resolutions in X.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-05 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 18:20 Why is the Powerbook Fn-Key handled differently? Matthias Grimm
2002-02-05 10:03 ` Michel Dänzer [this message]
2002-02-06 10:11 ` Michael Schmitz
2002-02-06 9:39 ` Michael Schmitz
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=1012903423.1594.533.camel@pismo \
--to=michel@daenzer.net \
--cc=joker@cymes.de \
--cc=linuxppc-dev@lists.linuxppc.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).