From: Stefan Seyfried <seife@suse.de>
To: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: nigel@suspend2.net, Pavel Machek <pavel@ucw.cz>,
LKML <linux-kernel@vger.kernel.org>,
dmitry.torokhov@gmail.com
Subject: Re: Failure to properly reinit i8042 post suspend-to-ram
Date: Tue, 10 Jul 2007 14:04:08 +0200 [thread overview]
Message-ID: <20070710120408.GA4188@suse.de> (raw)
In-Reply-To: <200707101059.57881.nigel@nigel.suspend2.net>
Hi,
On Tue, Jul 10, 2007 at 10:59:57AM +1000, Nigel Cunningham wrote:
> On Saturday 07 July 2007 01:04:51 Stefan Seyfried wrote:
> > On Thu, Jul 05, 2007 at 09:04:27PM +1000, Nigel Cunningham wrote:
> > >
> > > Adding i8042.reset=1 to the commandline fixed it.
> >
> > Wasn't there a quirk list where workarounds for i8042 on known bad machines
> > are stored? Maybe it would be a good idea to get your machine into it ;-)
>
> Unless I'm missing something, it looks like there's no such thing in the i8042
> driver. That's okay. I can cope with adding i8042.reset=1 to my
> commandline :)
In drivers/input/serio/i8042-x86ia64io.h there are tables for various quirks,
but apparently nothing for "reset=1".
If we find another machine that needs reset=1, then it might be time for a
table for this quirk.
Best regards,
Stefan
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
prev parent reply other threads:[~2007-07-10 15:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 6:07 Failure to properly reinit i8042 post suspend-to-ram Nigel Cunningham
2007-06-24 21:03 ` Rafael J. Wysocki
2007-06-24 23:18 ` Nigel Cunningham
2007-07-05 10:15 ` Pavel Machek
2007-07-05 11:04 ` Nigel Cunningham
2007-07-06 15:04 ` Stefan Seyfried
2007-07-06 23:01 ` Nigel Cunningham
2007-07-10 0:59 ` Nigel Cunningham
2007-07-10 12:04 ` Stefan Seyfried [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=20070710120408.GA4188@suse.de \
--to=seife@suse.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
--cc=nigel@suspend2.net \
--cc=pavel@ucw.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.