linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-input@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Vojtech Pavlik <vojtech@suse.cz>,
	Hans de Goede <hdegoede@redhat.com>,
	Jiri Kosina <jkosina@suse.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: i8042 - disable active multiplexing by default
Date: Mon, 13 Oct 2014 09:43:38 -0700	[thread overview]
Message-ID: <20141013164338.GA35440@dtor-ws> (raw)
In-Reply-To: <20141012143039.GC378@amd>

Hi Pavel,

On Sun, Oct 12, 2014 at 04:30:39PM +0200, Pavel Machek wrote:
> On Fri 2014-10-10 13:51:31, Dmitry Torokhov wrote:
> > Active multiplexing is a nice feature as it allows several pointing devices
> > (such as touchpad and external mouse) use their native protocols at the
> > same time. Unfortunately many manufacturers do not implement the feature
> > properly even though they advertise it. The problematic implementations are
> > never fixed, since Windows by default does not use this mode, and move from
> > one BIOS/model of laptop to another. When active multiplexing is broken
> > turning it on usually results in touchpad, keyboard, or both unresponsive.
> > 
> > With PS/2 usage on decline (most of PS/2 devices in use nowadays are
> > internal laptop touchpads), I expect number of users who have laptops with
> > working MUX implementation, docking stations with external PS/2 ports, and
> > who are still using external PS/2 mice, to be rather small. Let's flip the
> > default to be OFF and allow activating it through i8042.nomux=0 kernel
> > option.  We'll also keep DMI table where we can record known good models.
> > 
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> 
> Could we keep the old default / blacklist for the old laptops? We did
> something like that for ACPI, based on year of the bios.
> 

I would prefer not to. Unlike ACPI we do not see any improvement or
decline in quality of MUX implementation over time. The implementations
were buggy 10 years ago, 5 years go and they are buggy now. So there is
not a point in time to draw a line at.

> Old laptops are not being made any more, so blacklist will not grow
> too fast...

It is already quite big and I do not believe we've gotten nearly all of
them. I guess in many cases people would try Linux, find that
keyboard/mouse do not work at all and they are done and not bother
filing bugs/reaching out on LKML, etc.

Again, the only people would might be negatively affected are people who
have proper implementation of active MUX, who use both touchpad and
external mouse at the same time and want touchpad in native mode, and who
use PS/2 external mice.

Thanks.

-- 
Dmitry

      reply	other threads:[~2014-10-13 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 20:51 [PATCH] Input: i8042 - disable active multiplexing by default Dmitry Torokhov
2014-10-10 20:59 ` Jiri Kosina
2014-10-10 21:02   ` Dmitry Torokhov
2014-10-10 21:18 ` Dave Jones
2014-10-10 21:22   ` Dmitry Torokhov
2014-10-11  9:12     ` Hans de Goede
2014-10-12 14:30 ` Pavel Machek
2014-10-13 16:43   ` Dmitry Torokhov [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=20141013164338.GA35440@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=torvalds@linux-foundation.org \
    --cc=vojtech@suse.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 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).