public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Nico Schottelius <nico-kernel@schottelius.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Device files for keyboard(s)?
Date: Sat, 10 Dec 2005 09:49:28 -0500	[thread overview]
Message-ID: <200512100949.29185.dtor_core@ameritech.net> (raw)
In-Reply-To: <20051210085752.GF15679@schottelius.org>

On Saturday 10 December 2005 03:57, Nico Schottelius wrote:
> Hello dear Kernel-Developers,
> 
> I've the problem that I've connected two keyboards
> (one via usb and one via ps/2) to my machine and I want to have
> different keyboard layout on it.
> 
> While I was trying to find out what would be the best way to do that,
> I was somehow surprised that keyboards are not presented via
> a device file to userspace.
>

They are. You need to use event input interface. All input devices can
be accessed via /dev/input/eventX device nodes.
 
> My questions are:
> 
> - Is there a reason not to have devices for keyboards?
> - If I would implement it into a recent kernel, would it have any chance
>   getting into mainline?
> 
> I know this would have some consequences for user space, at least those:
> 
> - x11 (x.org/xfree) would have to modify their input device section for Linux
>   for keyboards
> - loadkeys would have to be patched so one could specify which keyboard
>   to change the layout for
> - kde/gnome would have to be changed in the manner that they support more
>   than one keyboard
> 
> Nico
> 
> P.S.: Please cc me.
> 

-- 
Dmitry

      reply	other threads:[~2005-12-10 14:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-10  8:57 Device files for keyboard(s)? Nico Schottelius
2005-12-10 14:49 ` Dmitry Torokhov [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=200512100949.29185.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico-kernel@schottelius.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