[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4B59D6F4-825C-4851-929F-DCA28A343B23@gmail.com>
Date: Thu, 27 May 2010 18:03:00 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Robert Hancock <hancockrwd@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
Bastien Nocera <hadess@...ess.net>
Subject: Re: [git pull] Input updates for 2.6.34-rc6
On May 27, 2010, at 5:46 PM, Linus Torvalds <torvalds@...ux-foundation.org
> wrote:
>
>
> On Thu, 27 May 2010, Robert Hancock wrote:
>>
>> It's highly unlikely that they are incomplete in this respect, as
>> since I mentioned, Windows would fail to recognize the PS/2
>> controller
>> that people would expect to work, which would most likely get
>> noticed..
>
> Did you miss the part where I actually quoted my own modern Core i5
> machine that _does_ have a keyboard controller, and _does_ have a
> keyboard
> port, and that does _not_ mention them in the PnP tables?
Except that it _does_. But _our_ ACPI implementation drops all
inactive devices so our PNP layer does not see your mouse and keyboard
ports.
>
>> I think this is a case where it has to be trusted, because that's
>> what
>> Windows does.
>
> The thing is, Windows isn't used for things like headless machines.
> Which
> we went over extensively in the thread. There's a _reason_ why Linux
> probes the dang thing.
--
Dmitry
--
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