Messages in this thread | | | Date | Tue, 3 Feb 2004 08:37:06 +0100 | From | Vojtech Pavlik <> | Subject | Re: FYI: ACPI 'sleep 1' resets atkbd keycodes |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |