From: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-input@vger.kernel.org, arjan@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch 1/2] input: introduce a tougher i8042.reset
Date: Thu, 5 Feb 2009 13:52:29 -0800 [thread overview]
Message-ID: <20090205135229.e4d5efc3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090204191631.21783c62@infradead.org>
On Wed, 4 Feb 2009 19:16:31 -0800
Arjan van de Ven <arjan@infradead.org> wrote:
> Some touchpads don't reset right the first time (MSI Wind U-100 for
> example). This patch will retry the reset up to 5 times.
Sigh, real life sucks. I wonder what the windows driver does.
> In addition, this patch also adds a module parameter to not treat
> reset failures as fatal to the usage of the device. This prevents
> a touchpad failure from also disabling the keyboard....
>
Is there any reason why we shouldn't just do this all the time?
IOW, is there any benefit in marking the 8042 as dead?
next prev parent reply other threads:[~2009-02-05 21:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 3:15 [patch 0/2] Make the touchpad on the MSI Wind netbook work Arjan van de Ven
2009-02-05 3:16 ` [patch 1/2] input: introduce a tougher i8042.reset Arjan van de Ven
2009-02-05 21:52 ` Andrew Morton [this message]
2009-02-06 0:35 ` Arjan van de Ven
2009-02-05 3:17 ` [patch 2/2] input: add a DMI table for the i8042.reset option; make MSI Wind U-100 work Arjan van de Ven
2009-02-06 0:21 ` Andrew Morton
2009-02-10 20:25 ` [patch 0/2] Make the touchpad on the MSI Wind netbook work Pavel Machek
2009-02-10 22:00 ` Rafael J. Wysocki
2009-02-11 1:00 ` Jiri Kosina
2009-02-11 1:13 ` Arjan van de Ven
2009-02-11 1:18 ` Jiri Kosina
2009-02-11 9:50 ` Rafael J. Wysocki
2009-02-10 23:06 ` Arjan van de Ven
2009-02-11 1:45 ` Matthew Garrett
2009-02-11 12:17 ` Jiri Kosina
2009-02-11 13:28 ` Andy Whitcroft
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=20090205135229.e4d5efc3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=linux-input@vger.kernel.org \
--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).