From: arno@natisbad.org (Arnaud Ebalard)
To: Luke-Jr <luke@dashjr.org>
Cc: linux-omap@vger.kernel.org
Subject: Re: N8x0 to mainline patches
Date: Mon, 20 Jul 2009 09:23:49 +0200 [thread overview]
Message-ID: <87ocrfhl6i.fsf@small.ssi.corp> (raw)
In-Reply-To: <200907191600.23502.luke@dashjr.org> (Luke-Jr's message of "Sun, 19 Jul 2009 16:00:19 -0500")
Hi,
"Luke-Jr" <luke@dashjr.org> writes:
>> When the rx44 keymap support is added back in your quilt set, can we
>> discuss it. IIRC, the same kind of value (i.e. > 255) is also in the
>> rx-51. Any specific reason?
>
> I presume the reason is that the "standard" code for the "Fn" key is 464... so
> it is only correct to map "Fn" to KEY_FN. ;)
I know, but from the document I read on the topic, xorg does not support
keycode value higher than 255. I must definitely be missing something.
> There is a software Fn key on some Mac laptops as well. Do they work? Why/how?
My old laptop was a powerbook 12" running Debian and that key never
worked, IIRC.
> Note: before I installed KDE 4 on my N810, Fn was working in X with its usual
> keycode...
If you manage to find out why/how it worked at some point, I am
interested.
Cheers,
a+
next prev parent reply other threads:[~2009-07-20 7:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 21:00 N8x0 to mainline patches Luke-Jr
2009-07-20 7:23 ` Arnaud Ebalard [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-13 14:49 Luke-Jr
2009-07-14 5:10 ` Kalle Valo
2009-07-15 16:19 ` Arnaud Ebalard
2009-07-13 5:51 Kalle Valo
2009-07-13 6:03 ` Felipe Balbi
2009-07-13 6:51 ` Kalle Valo
2009-07-13 6:53 ` Felipe Balbi
2009-08-06 7:10 ` Tony Lindgren
2009-08-06 16:21 ` Kalle Valo
2009-08-06 16:27 ` Kalle Valo
2009-08-07 7:03 ` Tony Lindgren
2009-08-07 7:44 ` Kalle Valo
2009-08-07 7:51 ` Tony Lindgren
2009-08-07 7:04 ` Tony Lindgren
2009-07-13 19:52 ` green
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=87ocrfhl6i.fsf@small.ssi.corp \
--to=arno@natisbad.org \
--cc=linux-omap@vger.kernel.org \
--cc=luke@dashjr.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