linux-kernel - Re: [PATCH 3/3] input: Default to only using PNP for i8042 probing on x86

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] [day] [month] [year] [list]

Message-ID: <20100514164200.GD31607@core.coreip.homeip.net>
Date:	Fri, 14 May 2010 09:42:01 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: Re: [PATCH 3/3] input: Default to only using PNP for i8042 probing
 on x86

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