From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Andries Brouwer <aebr@win.tue.nl>,
Roman Zippel <zippel@linux-m68k.org>,
linux-kernel@vger.kernel.org
Subject: Re: Possible bug in keyboard.c (2.6.10)
Date: Sat, 29 Jan 2005 18:30:24 -0500 [thread overview]
Message-ID: <200501291830.24532.dtor_core@ameritech.net> (raw)
In-Reply-To: <20050129111233.GA2268@ucw.cz>
On Saturday 29 January 2005 06:12, Vojtech Pavlik wrote:
> However, on 2.6, where you can have more than one keyboard, it'd be
> better to use the EVIOCSKEYCODE ioctl on the event device instead of the
> KDSKEYCODE ioctl on the console, as the later only changes the first
> found keyboard.
>
FWIW I changed atkbd so every keyboard has separate keymap (so one can set
one keyboard to set 2 and other to set 3). I think it should be possible to
adjust keymaps on individual keyboards to accurately map keys when keyboards
are different.
--
Dmitry
next prev parent reply other threads:[~2005-01-29 23:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 3:16 Possible bug in keyboard.c (2.6.10) Sasa Stevanovic
2005-01-27 4:50 ` Dmitry Torokhov
2005-01-27 10:16 ` Sasa Stevanovic
2005-01-27 12:56 ` Andries Brouwer
2005-01-28 0:39 ` Roman Zippel
2005-01-28 10:59 ` Vojtech Pavlik
2005-01-29 4:50 ` Al Viro
2005-01-29 11:25 ` Vojtech Pavlik
2005-01-29 23:35 ` Dmitry Torokhov
2005-01-31 9:01 ` Vojtech Pavlik
2005-01-30 8:41 ` Al Viro
2005-01-30 23:21 ` Dmitry Torokhov
2005-01-30 23:29 ` Dmitry Torokhov
2005-02-03 6:54 ` Dmitry Torokhov
2005-01-29 12:11 ` Roman Zippel
2005-01-29 14:04 ` Vojtech Pavlik
2005-01-30 20:13 ` Roman Zippel
2005-01-28 11:10 ` Vojtech Pavlik
2005-01-28 21:59 ` Andries Brouwer
2005-01-29 11:12 ` Vojtech Pavlik
2005-01-29 23:30 ` Dmitry Torokhov [this message]
2005-01-30 23:16 ` Pavel Machek
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=200501291830.24532.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
--cc=zippel@linux-m68k.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 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.