[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1005131410090.3711@i5.linux-foundation.org>
Date: Thu, 13 May 2010 14:21:52 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
cc: lenb@...nel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] Input updates for 2.6.34-rc6
On Thu, 13 May 2010, Dmitry Torokhov wrote:
>
> But I guess because there are no devices plugged in ACPI they are "inactive"
> and thus ACPI drop them. I was always wondered by ACPI did that. Len?
Btw, even without actual physically plugging in the device, at least the
really early KVM boxes used to basically just _physically_ switch between
keyboard ports, and so using such a KVM switch is essentially also going
to plug it in after boot time.
Some slightly more fancier KVM devices (probably most of them by now - if
you want auto-switching etc) have real electronics and actually emulate a
keyboard, needed for computers that require a keyboard to even boot up
("Keyboard not detected. Press F1 to continue").
But the hard-switching ones were at least at some point way more reliable:
the "smart" ones would have trouble with any "fancy" features like
scroll-wheels etc. Probably not an issue any more.
Of course, these days few people use PS/2 keyboards any more, but it would
still be a shame to break a perfectly reasonable setup.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists