public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: Cory Maccarrone <darkstar6262@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Modifying the kernel keymap
Date: Mon, 16 Nov 2009 00:31:05 +0200	[thread overview]
Message-ID: <1258324265.10351.1.camel@gandalf> (raw)
In-Reply-To: <6cb013310911151206s2496a6edxb3101d2d96c8dea0@mail.gmail.com>

Hi,

On Sun, 2009-11-15 at 12:06 -0800, Cory Maccarrone wrote:
> All,
> 
> I'm working with the Wing Linux and Linwizard projects in porting
> various omap850-based devices to Linux, and was wondering about
> keymaps.
> 
> In particular, I'm working with the HTC Herald, which uses an Alt key
> to access things like numbers and symbols on a physical keyboard.  In
> Linux, the keymappings are wrong for this -- Alt does something
> different and doesn't allow access to those extra characters.
> 
> In Linwizard, we've modified the defkeymap and added makefile rules to
> compile our modified defkeymap when a specific board was selected, but
> this isn't portable when building a kernel for many boards at once,
> each having a different mapping.
> 
> So, my question is, what is the best way to go about changing the
> defkeymap, or supplying a keymap that allows all the keys to function
> correctly, but doesn't require non-portable makefile hacks?

how about letting xmodmap handle that ? If you use alt key, then kernel
passes alt key. Userland can later remap that key to some other
function.

-- 
balbi



  reply	other threads:[~2009-11-15 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 20:06 Modifying the kernel keymap Cory Maccarrone
2009-11-15 22:31 ` Felipe Balbi [this message]
2009-11-15 22:42   ` Cory Maccarrone
2009-11-16 20:54     ` Tony Lindgren

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=1258324265.10351.1.camel@gandalf \
    --to=me@felipebalbi.com \
    --cc=darkstar6262@gmail.com \
    --cc=linux-omap@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