linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Jiri Kosina <jkosina@suse.cz>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: Add Acer Aspire 5710 to nomux blacklist
Date: Thu, 10 Jul 2014 10:45:51 +0200	[thread overview]
Message-ID: <20140710084551.GA26864@suse.cz> (raw)
In-Reply-To: <53BE4180.4030907@redhat.com>

On Thu, Jul 10, 2014 at 09:32:16AM +0200, Hans de Goede wrote:

> >>> I also expect
> >>> that most of external PS/2 mice are dead by now, so number of cases when
> >>
> >> One would at least hope so. Sadly, internal mice and PS/2 keyboards
> >> aren't going to go away any soon, due to larger power consumption of USB
> >> devices.
> > 
> > Right, but we are not talking about mouse vs keyboard, they use separate
> > ports anyway, it is touchpad plus external PS/2 mouse case where active
> > MUX might help.
> 
> What about laptops with both a touchpad and a trackpoint ? I think in most
> cases the trackpoint works through some sort of pass-through mode of the
> touchpad (or is outright part of the touchpad ps/2 device), but are we
> sure there are no cases where the trackpoint and touchpad are really
> separate ps/2 devices hookedup through an active mux ?

I'm not aware of any current machines using active multiplexing for
that. There are basically two touchpad manufacturers: Synaptics and
ALPS. Synaptics has a nearly transparent passthrough mode and
touchpoints are connected through that. ALPS basically manufactures a
touchpad+touchpoint combo device and thus doesn't need a fully
transparent passthrough.

Active multiplexing was typically used for external PS/2 ports on
laptops, because the manufacturer couldn't anticipate the protocol of
the externally connected device.

> >>> we have users with PS/2 touchpad + external PS/2 mouse + working active
> >>> MUX is exceedingly small.
> >>>
> >>> Let's pull Vojtech in ;)
> >>
> >> What I'd prefer is to, based on DMI data, report but not enable by
> >> default Active MUX mode on any machine manufactured after a certain
> >> date. Plus have a DMI-based whitelist for machines that absolutely
> >> needed, if any are found later.
> > 
> > Looking at the changes to nomux blacklist sometimes even trying MUX
> > messes up KBC. Instead of playing date games I'd rather simply make
> > i8042.nomux default. I'm fine with having whitelist for boxes that
> > actually need and support muxing properly.
> 
> I'm a bit skeptical about making this change, see above.

I'm not too keen about it either, as it could break existing setups. 

But I have to concede that any working hardware still using both
external and internal PS/2 and thus needing Active Multiplexing is most
likely to be found in museums today.

So the risk of breakage isn't all that big.

-- 
Vojtech Pavlik
Director SUSE Labs

  reply	other threads:[~2014-07-10  8:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  9:42 [PATCH] Input: Add Acer Aspire 5710 to nomux blacklist Jiri Kosina
2014-07-09 16:54 ` Dmitry Torokhov
2014-07-09 17:48   ` Vojtech Pavlik
2014-07-09 19:38     ` Dmitry Torokhov
2014-07-10  7:32       ` Hans de Goede
2014-07-10  8:45         ` Vojtech Pavlik [this message]
2014-07-10 15:20           ` Hans de Goede
2014-07-10 21:11             ` Dmitry Torokhov
2014-07-11  7:10               ` Hans de Goede

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=20140710084551.GA26864@suse.cz \
    --to=vojtech@suse.cz \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.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).