linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jiri Kosina <jkosina@suse.cz>
Cc: David Miller <davem@davemloft.net>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, swetland@google.com,
	arve@android.com, linux@arm.linux.org.uk,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk, san@android.com,
	rlove@google.com, Greg KH <greg@kroah.com>
Subject: Re: defkeymap making machine useless (was Re: HTC Dream aka. t-mobile g1 support)
Date: Mon, 22 Jun 2009 19:22:02 +0200	[thread overview]
Message-ID: <20090622172201.GA21153@elf.ucw.cz> (raw)
In-Reply-To: <alpine.LNX.2.00.0906221131380.7457@wotan.suse.de>

On Mon 2009-06-22 11:33:31, Jiri Kosina wrote:
> On Fri, 19 Jun 2009, Pavel Machek wrote:
> 
> > > > Yeah, I wasn't sure how to handle this.  We try to keep the 
> > > > msm/dream stuff in a state that doesn't break other parts of the 
> > > > tree, but there doesn't seem to be support for different keymaps for 
> > > > different devices.
> > > How it's supposed to work is that you have a specific keyboard driver 
> > > and that emits PC keyboard codes into the core kernel using a 
> > > translation table in your driver.
> > Of course, Dream does  that.  But that's not _nearly_ enough. Dream
> > lacks keys such as: esc, arrows, symbols (/;'[]\-=). That means that
> > for +, you can't press shift-=, you need to press altgr-P.
> 
> I don't seem to have enough context, but wouldn't writing a separate serio 
> driver, which would do all the needed translations be enough here?

Umm.

Yes, we could parse the keyboard combinations in the keyboard driver,
and then emulate the PC keyboard. It would be incredibly ugly. Such as:

If user presses Alt+I, (labeled "-" on keyboard), emulate "Shift+="
press, then let the defkeymap.map translate it back to "-".

I... guess it will be nicer if the keyboard driver specifies which
keymap to use?
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2009-06-22 17:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d6200be20906171436y5280ed8do561d2d53d73ca78@mail.gmail.com>
     [not found] ` <20090618101309.GC28892@elf.ucw.cz>
     [not found]   ` <a55d774e0906181233p35b60cd2ga401bd1304267643@mail.gmail.com>
     [not found]     ` <20090618.123845.232783995.davem@davemloft.net>
2009-06-18 23:07       ` defkeymap making machine useless (was Re: HTC Dream aka. t-mobile g1 support) Pavel Machek
2009-06-22  9:33         ` Jiri Kosina
2009-06-22 17:22           ` Pavel Machek [this message]

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=20090622172201.GA21153@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=arve@android.com \
    --cc=davem@davemloft.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=greg@kroah.com \
    --cc=jkosina@suse.cz \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rlove@google.com \
    --cc=san@android.com \
    --cc=swetland@google.com \
    /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).