From: Andrew Morton <akpm@linux-foundation.org>
To: Chris Lalancette <clalance@redhat.com>
Cc: linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com,
linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH]: Add command-line option to i8042 to completely disable it
Date: Wed, 25 Jul 2007 00:05:04 -0700 [thread overview]
Message-ID: <20070725000504.f8ce49c1.akpm@linux-foundation.org> (raw)
In-Reply-To: <46A4DFD2.2010501@redhat.com>
On Mon, 23 Jul 2007 13:05:22 -0400 Chris Lalancette <clalance@redhat.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?
next prev parent reply other threads:[~2007-07-25 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 17:05 [PATCH]: Add command-line option to i8042 to completely disable it Chris Lalancette
2007-07-25 7:05 ` Andrew Morton [this message]
2007-07-25 8:03 ` Vojtech Pavlik
2007-07-25 13:35 ` Chris Lalancette
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=20070725000504.f8ce49c1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clalance@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.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).