From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: "P. Christeas" <p_christ@hol.gr>,
acpi-devel@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: FYI: ACPI 'sleep 1' resets atkbd keycodes
Date: Tue, 3 Feb 2004 08:37:06 +0100 [thread overview]
Message-ID: <20040203073706.GE337@ucw.cz> (raw)
In-Reply-To: <200402022338.48010.dtor_core@ameritech.net>
On Mon, Feb 02, 2004 at 11:38:41PM -0500, Dmitry Torokhov wrote:
> I feel a little uneasy about killing the input device if set changes after
> resume. That would cause a new input device created but for user it would
> look like keyboard is lost or am I missing someting?
The console will automatically and immediately grab the new keyboard and
everything will continue to work, even X, because it uses the console
for input.
Later, when X uses the event interface, it'll get a notification that
the keyboard was removed and added again, which will cause it to open
the new one, so all will be OK, too.
> What about the patch below which would reset keyboard to the default keymap
> only if set changes?
I don't think there is a problem with just reconnecting. It's extremely
unlikely that the set can change, too, because everyone uses translated
set 2, and that's the lowest common denominator.
Unless you specified extra arguments on the kernel command line, you
can't get any other set.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-02-03 7:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 9:37 FYI: ACPI 'sleep 1' resets atkbd keycodes P. Christeas
2004-01-25 10:50 ` Vojtech Pavlik
2004-01-25 11:59 ` Vojtech Pavlik
2004-01-26 17:42 ` P. Christeas
2004-02-03 4:38 ` Dmitry Torokhov
2004-02-03 7:37 ` Vojtech Pavlik [this message]
2004-01-26 23:41 ` bill davidsen
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 6:27 Yu, Luming
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=20040203073706.GE337@ucw.cz \
--to=vojtech@suse.cz \
--cc=acpi-devel@lists.sourceforge.net \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=p_christ@hol.gr \
/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