From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: [git pull] Input updates for 2.6.34-rc6 Date: Fri, 14 May 2010 08:16:34 -0700 (PDT) Message-ID: References: <20100513075728.GF30110@core.coreip.homeip.net> <20100514145539.GA5598@srcf.ucam.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from smtp1.linux-foundation.org ([140.211.169.13]:57685 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751140Ab0ENPSx (ORCPT ); Fri, 14 May 2010 11:18:53 -0400 In-Reply-To: <20100514145539.GA5598@srcf.ucam.org> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Matthew Garrett Cc: Dmitry Torokhov , Andrew Morton , Linux Kernel Mailing List , linux-input@vger.kernel.org, Bastien Nocera On Fri, 14 May 2010, Matthew Garrett wrote: > > I've done some experimentation under qemu. On ACPI systems, Windows will > *only* touch the keyboard controller if there's a device with an > appropriate PNP HID or CID and if _STA evaluates to 0x0b or 0x0f. > Otherwise it'll simply ignore the hardware entirely. By the looks of it > their keyboard probing is also somewhat different to ours, but that's > probably another story. Well, I'd hate to lose the keyboard hotplug capability, but at the same time, it _is_ 2010, and while I have personally used it historically, I don't really foresee ever using it again. So we _could_ decide to just try it, and see if anybody screams. If nobody does, that would be a very simple solution to the problem. Linus