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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <alpine.LFD.2.00.1005200054090.2921@localhost.localdomain>
Date:	Thu, 20 May 2010 00:56:18 -0400 (EDT)
From:	Len Brown <lenb@...nel.org>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.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:

> 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.

cheers,
Len Brown, Intel Open Source Technology Center

--
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/