All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Alfred E. Heggestad" <aeh@db.org>, linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] USB: driver for CM109 chipset
Date: Fri, 13 Jul 2007 00:38:08 +0200	[thread overview]
Message-ID: <20070712223808.GD8858@suse.cz> (raw)
In-Reply-To: <d120d5000707120922m3c821ed8ia827dab20ad599f5@mail.gmail.com>

On Thu, Jul 12, 2007 at 12:22:10PM -0400, Dmitry Torokhov wrote:

> >> Hmm, they use KEY_0 through KEY_9 now.
> >
> >Which results in the phone sending 'é+ěščřžýáí' instead of 
> >'0123456789'
> >on a Czech keyboard, which is definitely not what's intended. Similarly
> >for many other European keyboards.
> >
> 
> Hmm, I uttely confused. Why when atkbd emits KEY_0 it you get 0 in the
> shell (don't you?) but different result with phone keypad?

No, on a Czech keyboard you don't. You press KEY_0, you get 'é'. The
French layout gives sililar results. (For '0' you need to press
KEY_SHIFT KEY_0.)

> >I'll have to figure out where does KEY_103RD come from. I believe it was
> >defined as a key similar to KEY_102ND on specific national keyboards.
> >Brazil springs to mind, but I might be completely wrong. If it's not in
> >use today, we might as well kill it and reuse the code.
> 
> You had it in the beginning but it was removed around 2.6.2 so 84 is
> free at the moment.

OK then.

> >I don't think that it'd be a huge problem to expand KEY_MAX. I'm not
> >entirely convinced we want to have a different event code for every
> >different key numbered '5'.
> 
> But they are different as in people expect different actions when they
> press 5 on the keyboard, keypad, remote control and phone, don't they?

Maybe yes. If they had a input device from hell combining all this
functionality into one, they'd likely still want to differentiate
between the keys.

> Well, maybe not... I can argue both ways I guess... It's more like
> people may not want input from certain devices be used by certain
> programs (like they don't like RC cause numbers to be printed in the
> shell). 

But people like the fact that the 'voip' phone devices type regular keys
into the voip client programs, because that's what the programs expect,
the keys typed on a regular keyboard ...

You can't win in all cases.

> So far they used grabbing on the devices but I don't think
> this is sustainable in the long run.

They likely want per-device keymaps. This would also allow to have two
keyboards, with different language layouts, connected at the same time.
I know a number of people asked how to do that in the past.

-- 
Vojtech Pavlik
Director SuSE Labs

  reply	other threads:[~2007-07-12 22:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 13:49 [PATCH] USB: driver for CM109 chipset Alfred E. Heggestad
2007-06-25 14:29 ` Dmitry Torokhov
2007-06-25 22:29   ` Alfred E. Heggestad
2007-07-02 15:37   ` Vojtech Pavlik
2007-07-12 14:47     ` Dmitry Torokhov
2007-07-12 15:25       ` Vojtech Pavlik
2007-07-12 16:22         ` Dmitry Torokhov
2007-07-12 22:38           ` Vojtech Pavlik [this message]
2007-07-20 19:14             ` Dmitry Torokhov
2007-07-21  8:16               ` Vojtech Pavlik
  -- strict thread matches above, loose matches on Subject: below --
2007-06-26 19:52 Alfred E. Heggestad
2007-08-29 16:39 Alfred E. Heggestad

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=20070712223808.GD8858@suse.cz \
    --to=vojtech@suse.cz \
    --cc=aeh@db.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.