From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH 3/3] input: Default to only using PNP for i8042 probing on x86
Date: Fri, 14 May 2010 09:42:01 -0700 [thread overview]
Message-ID: <20100514164200.GD31607@core.coreip.homeip.net> (raw)
In-Reply-To: <20100514163643.GB7843@srcf.ucam.org>
On Fri, May 14, 2010 at 05:36:43PM +0100, Matthew Garrett wrote:
> On Fri, May 14, 2010 at 09:31:59AM -0700, Dmitry Torokhov wrote:
> > On Fri, May 14, 2010 at 12:10:03PM -0400, Matthew Garrett wrote:
> > > Experimenting with Windows has revealed that it will not probe the
> > > keyboard controller unless a valid PNPACPI device is present. Change our
> > > behaviour to match, and add a new i8042.forcedprobe parameter to allow
> > > people to override it.
> > >
> >
> > i8042.nopnp would not do?
>
> It could - it wouldn't be quite semantically equivalent, but I don't see
> why it wouldn't work.
>
I think they are exactly equivalent - "piss on what PNP says, bang the ports
directly".
--
Dmitry
prev parent reply other threads:[~2010-05-14 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 16:10 [PATCH 1/3] input: Add some extra PNP keyboard types Matthew Garrett
2010-05-14 16:10 ` [PATCH 2/3] input: Add a PNP entry to the aux device list Matthew Garrett
2010-05-14 16:10 ` [PATCH 3/3] input: Default to only using PNP for i8042 probing on x86 Matthew Garrett
2010-05-14 16:15 ` Randy Dunlap
2010-05-14 16:19 ` Linus Torvalds
2010-05-14 16:31 ` Dmitry Torokhov
2010-05-14 16:36 ` Matthew Garrett
2010-05-14 16:42 ` Dmitry Torokhov [this message]
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=20100514164200.GD31607@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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).