From: Andres Salomon <dilinger@queued.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
dsd@laptop.org, pgf@laptop.org, James Cameron <quozl@laptop.org>
Subject: Re: [PATCH] psmouse: disable the synaptics extension on OLPC machines.
Date: Fri, 17 Dec 2010 22:14:47 -0800 [thread overview]
Message-ID: <20101217221447.375b9977@queued.net> (raw)
In-Reply-To: <20101218054927.GA14718@core.coreip.homeip.net>
On Fri, 17 Dec 2010 21:49:28 -0800
Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> On Fri, Dec 17, 2010 at 09:09:39PM -0800, Andres Salomon wrote:
> >
> > OLPC has switched to a Synaptics touchpad. It turns out that it's
> > pretty useless in absolute mode. This patch looks for an OLPC
> > system (via DMI tables), and refuses to init Synaptics mode in
> > that scenario (falling back to relative mode).
> >
> > Signed-off-by: Andres Salomon <dilinger@queued.net>
>
> Andres,
>
> Can we do what hgpk does and add "depend on !OLPC" to the Kconfig
> instead?
>
> Thanks.
>
That wouldn't work for distro kernels, unfortunately. Currently the
kernels that OLPC releases disable CONFIG_MOUSE_PS2_SYNAPTICS. I'd
like to use a stock distribution kernel, which would need to enable
both CONFIG_OLPC *and* CONFIG_MOUSE_PS2_SYNAPTICS.. Hence the
motivation for this patch. :)
next prev parent reply other threads:[~2010-12-18 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 5:09 [PATCH] psmouse: disable the synaptics extension on OLPC machines Andres Salomon
2010-12-18 5:49 ` Dmitry Torokhov
2010-12-18 6:14 ` Andres Salomon [this message]
2010-12-18 7:02 ` Dmitry Torokhov
2010-12-18 10:00 ` Daniel Drake
2010-12-19 8:20 ` Dmitry Torokhov
2010-12-19 8:32 ` Andres Salomon
2010-12-19 8:37 ` Dmitry Torokhov
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=20101217221447.375b9977@queued.net \
--to=dilinger@queued.net \
--cc=dmitry.torokhov@gmail.com \
--cc=dsd@laptop.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgf@laptop.org \
--cc=quozl@laptop.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 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.