linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	Bastien Nocera <hadess@hadess.net>
Subject: Re: [git pull] Input updates for 2.6.34-rc6
Date: Thu, 27 May 2010 22:10:20 -0700	[thread overview]
Message-ID: <20100528051020.GC2663@core.coreip.homeip.net> (raw)
In-Reply-To: <4BFF4120.7030501@gmail.com>

On Thu, May 27, 2010 at 10:05:52PM -0600, Robert Hancock wrote:
> On 05/27/2010 07:03 PM, Dmitry Torokhov wrote:
> >On May 27, 2010, at 5:46 PM, Linus Torvalds
> ><torvalds@linux-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.
> 
> That's likely true - 

This was not a guess - I have seen DSDT from Linus' box.

That is why I said I'd be happy applying Metthew's patch if our ACPI did
not drop inactive devices - it would leave Apple and newer boxes alone
while still allowing plugging in keyboard/mouse in boxes that do have
i8042 even if BIOS decided to hide it from Windows.

-- 
Dmitry

  reply	other threads:[~2010-05-28  5:10 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13  7:57 [git pull] Input updates for 2.6.34-rc6 Dmitry Torokhov
2010-05-13 14:35 ` Linus Torvalds
2010-05-13 14:47   ` Bastien Nocera
2010-05-13 15:04     ` Linus Torvalds
2010-05-13 15:19       ` Linus Torvalds
2010-05-13 15:50       ` Dmitry Torokhov
2010-05-13 16:16         ` Linus Torvalds
2010-05-13 16:38           ` Randy Dunlap
2010-05-13 20:15         ` Matthew Garrett
2010-05-13 16:01   ` Dmitry Torokhov
2010-05-13 16:54     ` Linus Torvalds
2010-05-13 16:58       ` Linus Torvalds
2010-05-13 17:16       ` Dmitry Torokhov
2010-05-13 17:30         ` Linus Torvalds
2010-05-13 18:10           ` Dmitry Torokhov
2010-05-13 19:55             ` Linus Torvalds
2010-05-14  7:56               ` Eric W. Biederman
2010-05-14 14:54                 ` Linus Torvalds
2010-05-14 15:38                   ` Matthew Garrett
2010-05-14 15:42                     ` Linus Torvalds
2010-05-14 15:49                       ` Matthew Garrett
2010-05-20  4:53                         ` Len Brown
2010-05-27  6:22       ` Robert Hancock
2010-05-27  6:43         ` Dmitry Torokhov
2010-05-27 17:06         ` Linus Torvalds
2010-05-27 23:03           ` Robert Hancock
2010-05-28  0:46             ` Linus Torvalds
2010-05-28  1:03               ` Dmitry Torokhov
2010-05-28  4:05                 ` Robert Hancock
2010-05-28  5:10                   ` Dmitry Torokhov [this message]
2010-05-14 14:55   ` Matthew Garrett
2010-05-14 15:16     ` Linus Torvalds
2010-05-14 16:28       ` Dmitry Torokhov
2010-05-14 18:47       ` david
2010-05-14 18:49         ` Matthew Garrett
2010-05-14 18:55           ` david
2010-05-14 18:59             ` Matthew Garrett
2010-05-14 19:05             ` david
2010-05-28  2:38       ` Mike Frysinger
2010-08-04  6:20       ` Dmitry Torokhov
2010-08-04  6:29         ` Dmitry Torokhov
2010-05-14 16:29     ` Dmitry Torokhov
2010-05-14 16:35       ` Matthew Garrett
  -- strict thread matches above, loose matches on Subject: below --
2010-05-05  6:41 Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100528051020.GC2663@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hadess@hadess.net \
    --cc=hancockrwd@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).