linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Keyboard and keymaps
Date: Wed, 7 Apr 1999 15:46:57 +0200	[thread overview]
Message-ID: <19990407154657.012380@mail.mipsys.com> (raw)


While I'm working on ADB, I would like to also fix the problem of
linux-pmac lacking international keymaps for all Apple keyboards.

Basically, I plan to build some kind of conversion tool that takes Apple
KCHRs and build the appropriate linux keymaps.

Could someone point me to the appropriate documentation or how-to's about
linux keybaord handling, I must admit I'm a little bit lost. If I
undestand things correctly, keymaps are somewhat "compiled" and then
copied inside the kernel by the userland tools from the kbd package. Is
there some specific documentation about this or should I just spend more
time reading the source ? Are the tables in mac_keyb.c the ones that are
replaced by userland, or is there a 2-tables indirection ?

How does linux handle dead keys and things like that ?

And finally, I think there's a different mecanism for X. I would
appreciate if someone could point me to the correct documentations for
all this or give me a quick explanation on the "big picture", I can then
figure out the details from the source.


-- 
           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. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

                 reply	other threads:[~1999-04-07 13:46 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=19990407154657.012380@mail.mipsys.com \
    --to=bh40@calva.net \
    --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).