From: Jiri Kosina <jkosina@suse.cz>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [patch 0/2] Make the touchpad on the MSI Wind netbook work
Date: Wed, 11 Feb 2009 02:18:48 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.1.10.0902110216190.11630@jikos.suse.cz> (raw)
In-Reply-To: <20090210171358.78c34d41@infradead.org>
On Tue, 10 Feb 2009, Arjan van de Ven wrote:
> > > From what I have heard there are different models of MSI Wind out
> > > there, with different set of hardware configurations.
> > Arjan, Rafael, could you please provide the dmidecode outputs for the
> > working and non-working systems, so that we can see what are the
> > differences?
> does this matter for the patch ?
Only in a very minor way -- if the board name in the DMI is the same, we
could avoid performing the extra resets when not needed by specifying a
different DMI match criteria.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2009-02-11 1:18 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
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 [this message]
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=alpine.LNX.1.10.0902110216190.11630@jikos.suse.cz \
--to=jkosina@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/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).