mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Patch for atkbd.c from Ubuntu
Date: Mon, 29 May 2006 00:59:31 -0400	[thread overview]
Message-ID: <200605290059.32302.dtor_core@ameritech.net> (raw)
In-Reply-To: <20060524113139.e457d3a8.zaitcev@redhat.com>

On Wednesday 24 May 2006 14:31, Pete Zaitcev wrote:
> Hi, Dmitry:
> 
> What do you think about the attached? Apparently, this is needed to
> support Korean input keys. Please let me know if this can be included.
> 
> Here's a bug entry for reference:
>  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192637
>

Hi Pete,

Please look here:

	http://bugzilla.kernel.org/show_bug.cgi?id=2817#c4

"I will not accept this patch (or any similar patch) to extend the atkbd.c
mapping table - only standard scancodes are allowed there. The table is
easily modified from userspace, and that is the way to go.

In the past I tried to fill the table with all the entries, but found out
that there are two or three keyboards competing for every position in the
scancode table, with a different keycode."

I continue to agree with Vojtech's position here. Because kernel does not
have ability to detect the kind of keyboard connected to a box (nor do we
really want to store all this data in the kernel) all fine tuning of AT
keymap should be done from userspace.

-- 
Dmitry

  reply	other threads:[~2006-05-29  4:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24 18:31 Pete Zaitcev
2006-05-29  4:59 ` Dmitry Torokhov [this message]
2006-05-29  6:34   ` Pete Zaitcev
2006-06-12  4:49     ` Dmitry Torokhov
2006-06-12  7:26       ` Pete Zaitcev
2006-06-12 16:01         ` Jerome Pinot
2006-06-12 16:16           ` Dmitry Torokhov
2006-06-12 16:51             ` Jerome Pinot

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=200605290059.32302.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.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

all inboxes | Powered by JetHome®