| 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
| ||
|
Date: Wed, 25 Jul 2007 00:05:04 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Chris Lalancette <clalance@...hat.com> Cc: linux-kernel@...r.kernel.org, dmitry.torokhov@...il.com, linux-input@...ey.karlin.mff.cuni.cz Subject: Re: [PATCH]: Add command-line option to i8042 to completely disable it On Mon, 23 Jul 2007 13:05:22 -0400 Chris Lalancette <clalance@...hat.com> wrote: > (I tried to send this patch to linux-input@, but it seems to be currently having > some problems, so I'm going directly to LKML). > > Certain (broken) pieces of South Bridge hardware will respond to > i8042_read_status() on boot with 0x0, despite there not being a real i8042 > controller hooked up in the south bridge. This can cause the detection for the > i8042 to return a "phantom" device, which hangs up later initialization. Note > that using "i8042.nokbd" and/or "i8042.noaux" do not help with this, since this > shows up during i8042_controller_check() (before either of those options are > checked). This patch adds a command-line option "i8042.disable", which just > completely disables any checking for the i8042 controller. That's an unfortunate fix. Is there really no way in which we can auto-detect such a situation without requiring a manual setting? - 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