Input updates for 2.6.34-rc6
in [Kernel]
|
Prev: HWPOISON for hugepage (v5)
Next: gta02: Use pcf50633 backlight driver instead of platform backlight driver.
From: Dmitry Torokhov on 14 May 2010 12:30 On Fri, May 14, 2010 at 08:16:34AM -0700, Linus Torvalds wrote: > > > 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. > FWIW we also using active multiplexing while windows does not as far as I know. I'd like us to be better than them. > 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 -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Matthew Garrett on 14 May 2010 12:40 On Fri, May 14, 2010 at 09:29:52AM -0700, Dmitry Torokhov wrote: > On Fri, May 14, 2010 at 03:55:39PM +0100, 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. > > > > However, I did find a couple of device IDs that machines may produce > > which we don't currently check for. I'll send a patch. > > > > I was wondering if we should be matching for _CID instead of _HID for > mouse and keyboard. I'm pretty sure the PNP layer will bind to either _HID or _CID. -- Matthew Garrett | mjg59(a)srcf.ucam.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Dmitry Torokhov on 14 May 2010 12:40 On Fri, May 14, 2010 at 03:55:39PM +0100, 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. > > However, I did find a couple of device IDs that machines may produce > which we don't currently check for. I'll send a patch. > I was wondering if we should be matching for _CID instead of _HID for mouse and keyboard. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: david on 14 May 2010 14:50 On Fri, 14 May 2010, Linus Torvalds wrote: > 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. this is actually fairly common in datacenter environments where people plug in crash carts to problem machines. yes, everything has USB ports, so they could use USB keyboards, but it's actually pretty common to still use PS/2 keyboards (and while the systems all support USB, it's not uncommon to have KVM systems, including pretty expensive 'enterprise' KVM systems that still require PS/2 keyboards be used to plug into the KVM, so those are the keyboards that are in the datacenter that someone will grab to plug into a problem machine) David Lang -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Matthew Garrett on 14 May 2010 15:00
On Fri, May 14, 2010 at 11:47:43AM -0700, david(a)lang.hm wrote: > yes, everything has USB ports, so they could use USB keyboards, but it's > actually pretty common to still use PS/2 keyboards (and while the systems > all support USB, it's not uncommon to have KVM systems, including pretty > expensive 'enterprise' KVM systems that still require PS/2 keyboards be > used to plug into the KVM, so those are the keyboards that are in the > datacenter that someone will grab to plug into a problem machine) The server hardware I've looked at will all declare the ports regardless of whether or not there's something plugged in. -- Matthew Garrett | mjg59(a)srcf.ucam.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |