All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yves-Alexis Perez <corsac@debian.org>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Andrew Duggan <aduggan@synaptics.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Peter Hutterer <peter.hutterer@who-t.net>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] New Lenovos 2015 touchpads: party time!
Date: Thu, 19 Mar 2015 16:25:27 +0100	[thread overview]
Message-ID: <20150319152526.GA3651@balvenie> (raw)
In-Reply-To: <20150319144627.GA18134@mail.corp.redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Thu, Mar 19, 2015 at 10:46:27AM -0400, Benjamin Tissoires wrote:
> On Mar 19 2015 or thereabouts, Yves-Alexis Perez wrote:
> > So I have two questions/remarks about this:
> > 
> > - if I don't use the touchpad, do I need xf86-input-synaptics at all?
> 
> Wether you use it or not, with the current kernel patch set, there will
> be no modifications to do in xf86-input-synaptics. Legacy versions will
> work just fine and the trackstick/touchpads are seen like they were in
> the past (lik ein the thinkpads t410 .. t430).
> 
> So I would advice to just revert to whatever Xorg / xf86-input-synaptics
> / configuration you had from your distribution, apply the patches (or
> wait for 4.0-rc5), and you are done.

So to summarize: both patchsets are enough for complete
touchpad+trackpoint operations, having both is not useful but not
harmful either, and it's better to have the kernel one.

Am I right? Thanks for the information, I'll also try to point our
kernel maintainers to that thread and ask them if it's possible to
backport them to the 3.16 kernel for Jessie.
> 
> > - how can I have the BIOS setting respected by the psmouse/synaptics
> >   kernel module (like when using psmouse)
> 
> I was confused at first so I double checked. If you use the
> psmouse.proto=imps boot parameter, then the bios setting is respected.
> 
> If the trackpad is enabled, it is barely usable, but that's what you get
> :)

Oh ok. I didn't try to boot with touchpad enabled in BIOS and
psmouse.proto=imps, so I missed that.

But that doesn't really answer my question. Can the BIOS setting be
handled correctly, so I don't have to disable the touchpad from xinput
or something?

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCgAGBQJVCupjAAoJEG3bU/KmdcClcikH/2e5qahRr2+gXRbEzQcimMvp
9EHk7cY+1AQlDfN5EasKY3mEbYUC7ZZP97IlKZSTCgcl8Ai8d+jYAMlkOviytV5x
eh8LixhI/0d4u/SBDycXYXezMaNqdVQYBJ+E8bEHM6SXp4h1qEHlhzeIwDDafWQk
UeVFWbQAxrWSXX+6ZCrmBNqDOvKdCddAa77DjZGhOztBrnk4+Kr2CvcurNiHJ/36
Z1gdSaVk9Or8hfwxcoT5ZMGXld+CihK0MMuwSLBoHjggHjGFkDZuQM6I3l8WAQO5
uMjQhp+s3Gt2raMYwSFDSQQ2Tlc7//nh6LySIkPVUU+uaG3W2xbhOUFHnauLW1I=
=xG6T
-----END PGP SIGNATURE-----

  reply	other threads:[~2015-03-19 15:25 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 20:04 [PATCH v2 0/7] New Lenovos 2015 touchpads: party time! Benjamin Tissoires
2015-02-06 20:04 ` [PATCH v2 1/7] Input: synaptics - fix middle button on Lenovo 2015 products Benjamin Tissoires
2015-02-06 20:04 ` [PATCH v2 2/7] Input: synaptics - handle spurious release of trackstick buttons Benjamin Tissoires
2015-02-06 20:04 ` [PATCH v2 3/7] Input: synaptics - do not retrieve the board id on old firmwares Benjamin Tissoires
2015-02-06 20:04 ` [PATCH v2 4/7] Input: synaptics - retrieve the extended capabilities in query $10 Benjamin Tissoires
2015-02-06 20:04 ` [PATCH v2 5/7] Input: synaptics - remove TOPBUTTONPAD property for Lenovos 2015 Benjamin Tissoires
2015-02-06 20:04 ` [PATCH v2 6/7] Input: synaptics - re-route tracksticks buttons on the Lenovo 2015 series Benjamin Tissoires
2015-03-09  6:45   ` Dmitry Torokhov
2015-02-06 20:04 ` [PATCH v2 7/7] Input: synaptics - Remove X1 Carbon 3rd gen from the topbuttonpad list Benjamin Tissoires
2015-02-17  3:23 ` [PATCH v2 0/7] New Lenovos 2015 touchpads: party time! Benjamin Tissoires
2015-02-25 14:36   ` Benjamin Tissoires
2015-02-25 14:58     ` Hans de Goede
2015-03-09  6:46       ` Dmitry Torokhov
2015-03-09  8:24         ` Hans de Goede
2015-03-09 19:36           ` Benjamin Tissoires
2015-03-10  6:17             ` Steven Noonan
2015-03-10  7:23               ` Hans de Goede
2015-03-10 18:35                 ` Steven Noonan
2015-03-16 14:46             ` Benjamin Tissoires
2015-03-19 14:24 ` Yves-Alexis Perez
2015-03-19 14:24   ` Yves-Alexis Perez
2015-03-19 14:46   ` Benjamin Tissoires
2015-03-19 15:25     ` Yves-Alexis Perez [this message]
2015-03-19 15:58       ` Benjamin Tissoires
2015-03-19 16:47         ` Yves-Alexis Perez
2015-03-19 16:47           ` Yves-Alexis Perez
2015-03-19 17:06           ` Benjamin Tissoires
2015-03-19 17:43             ` Dmitry Torokhov
2015-03-19 18:29               ` Benjamin Tissoires
2015-03-19 18:29                 ` Benjamin Tissoires
2015-03-20 13:59             ` Yves-Alexis Perez
2015-04-09 12:59         ` Yves-Alexis Perez
2015-04-09 13:56           ` Benjamin Tissoires
  -- strict thread matches above, loose matches on Subject: below --
2015-02-21 23:22 Michael Mullin

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=20150319152526.GA3651@balvenie \
    --to=corsac@debian.org \
    --cc=aduggan@synaptics.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.hutterer@who-t.net \
    /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.