From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org, Paul Mackerras <paulus@cs.anu.edu.au>
Cc: Cort Dougan <cort@ladron.cs.nmt.edu>
Subject: Bogus mouse key events
Date: Mon, 1 Feb 1999 22:18:53 +0100 [thread overview]
Message-ID: <19990201221853.005850@mail.mipsys.com> (raw)
I finally found where my conflicts on the PowerBook G3 Series and the
"Fn" key came from. It's simple: the "fake" keycode used by the console
code (and so by Xpmac) for the middle button is 0x3f, which is also the
keycode used by this "Fn" key...
So either we change the middle key code in both the kernel and Xpmac, or
(simpler), we add code for remapping the "Fn" key to something else.
I'm not (yet) very familiar with the linux keymap and keycode-map, so I
would like someone who knows this better than me to suggest a keycode to
which I could remap the "Fn" key without conflicting. I was thinking
about the equivalent of PC's alt-gr, but it may cause other kind of trouble.
This key must be handled in a really special way, since it may be used as
a mouse button modifier (using the "adb_buttons=2,x,y" patch), but it
should be ingnored in some cases (page-up, page down for example) since
the keyboard hardware will automatically send the correct modified keycodes.
So, any suggestion for a new keycode that won't conflict with anyone ?
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
reply other threads:[~1999-02-01 21:18 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=19990201221853.005850@mail.mipsys.com \
--to=bh40@calva.net \
--cc=cort@ladron.cs.nmt.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@cs.anu.edu.au \
/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).