From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Roel Aaij <roel.aaij@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>, Pavel Machek <pavel@ucw.cz>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: Problems with Elantech touchpad in 3.18-rc2
Date: Fri, 31 Oct 2014 09:24:36 -0700 [thread overview]
Message-ID: <20141031162436.GA36996@dtor-ws> (raw)
In-Reply-To: <20141030192506.GH36444@dtor-ws>
On Thu, Oct 30, 2014 at 12:25:06PM -0700, Dmitry Torokhov wrote:
> On Thu, Oct 30, 2014 at 12:06:03PM -0700, Linus Torvalds wrote:
> > On Thu, Oct 30, 2014 at 11:03 AM, Dmitry Torokhov
> > <dmitry.torokhov@gmail.com> wrote:
> > >
> > > Linus, any guidance here? Can we live with such regression?
> >
> > No. If people are already finding machines with problems, that means
> > that there will be a lot of them once distributions move to that
> > kernel.
>
> My only argument here is that failure is much less severe than with MUX
> case: when in legacy mode the worst that is happening is that advanced
> features (multi-touch, two-finger scroilling, etc) do not work so the
> experience is similar to Windows box with no venrod drivers installed.
> Whereas when active MUX does not work but we are tying to use it your
> device is completely hosed.
So I slept on it and I decided that we should indeed revert the patch,
since it causes more grief to people with good hardware than I
expected. We should not punish owners of good hardware because some
vendors can't write their firmware.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2014-10-31 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 17:14 Problems with Elantech touchpad in 3.18-rc2 Roel Aaij
2014-10-30 18:03 ` Dmitry Torokhov
2014-10-30 19:06 ` Linus Torvalds
2014-10-30 19:25 ` Dmitry Torokhov
2014-10-31 16:24 ` Dmitry Torokhov [this message]
2014-10-31 17:30 ` Pavel Machek
2014-10-31 17:35 ` 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=20141031162436.GA36996@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=roel.aaij@gmail.com \
--cc=torvalds@linux-foundation.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).