Re: [git pull] Input updates for 2.6.34-rc6

From: Dmitry Torokhov
Date: Thu May 20 2010 - 03:15:48 EST


On Thu, May 20, 2010 at 12:56:18AM -0400, Len Brown wrote:
> On Thu, 13 May 2010, Dmitry Torokhov wrote:
>
> > On Thursday 13 May 2010 12:40:43 pm Linus Torvalds wrote:
> > > On Thu, 13 May 2010, Dmitry Torokhov wrote:
> > > > You don't have anything plugged into the ports though, do you?
> > >
> > > No. It's a modern machine. But the port is there, and we've been very good
> > > at booting up and finding keyboards later (I've done it myself - headless
> > > machines that you hotplug a PS/2 keyboard into: it's not necessarily
> > > technically something you're supposed to do, but it has worked fine for
> > > me).
> > >
> > > > I wonder what your DSDT looks like.
> >
> > [... pulling LKML back in...]
> >
> > Lookie, lookie:
> >
> > Device (PS2K)
> > {
> > Name (_HID, EisaId ("PNP0303"))
> > Name (_CID, EisaId ("PNP030B"))
> > Method (_STA, 0, NotSerialized)
> > {
> > ShiftLeft (One, 0x0A, Local0)
> > If (And (IOST, Local0))
> > {
> > Return (0x0F)
> > }
> >
> > Return (Zero)
> > }
> > ...
> >
> > Device (PS2M)
> > {
> > Name (_HID, EisaId ("PNP0F03"))
> > Name (_CID, EisaId ("PNP0F13"))
> > Method (_STA, 0, NotSerialized)
> > {
> >
> > 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?
>
> I guess only a Windows person could answer this --
> since it is really a Windows-ism, rather than something that
> makes any sense based on what is in the ACPI spec itself.
>

Then we should probably revisit this? I am not saying that we need to
try evaluating more than Windows does but we still should add the
devices into the tree so their presence can be detected.

--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/