All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Jiri Kosina <jkosina@suse.cz>,
	linux-input@vger.kernel.org, hdegoede@redhat.com
Subject: Re: [PATCH] Input: Add Acer Aspire 5710 to nomux blacklist
Date: Wed, 9 Jul 2014 12:38:31 -0700	[thread overview]
Message-ID: <20140709193830.GE10364@core.coreip.homeip.net> (raw)
In-Reply-To: <20140709174821.GA30912@suse.cz>

On Wed, Jul 09, 2014 at 07:48:21PM +0200, Vojtech Pavlik wrote:
> On Wed, Jul 09, 2014 at 09:54:38AM -0700, Dmitry Torokhov wrote:
> > On Wed, Jun 25, 2014 at 11:42:43AM +0200, Jiri Kosina wrote:
> > > Acer Aspire needs to be added to nomux blacklist, otherwise the touchpad 
> > > misbehaves rather randomly.
> > > 
> > > Signed-off-by: Jiri Kosina <jkosina@suse.cz>
> > > 
> > > ---
> > > 
> > > Hi Dmitry,
> > > 
> > > I've come across this a few year old patch originating from our internal 
> > > bugzilla, which was apparently been lost between the cracks somewhere. 
> > > We've been carrying it in our kernel tree for quite some time ... could 
> > > you please apply it? Thanks.
> > 
> > I will. I also wonder if by now we should stop defaulting to MUX mode:
> > all newer desktop/server boxes use USB, only laptops still use PS/2,
> 
> MUX mode was only ever available on laptops - no desktop computer I'm
> aware of ever had it.

Yeah, I don't recall seeing one either.

> 
> > and quite a few of them not implement active MUX properly. 
> 
> Do you still get reports of non-working, but advertized Active
> Multiplexing mode on new laptops?

Evey now and then... Vendors seem to not normally touch that code.

> 
> > 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.

> 
> > 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.

Thanks.

-- 
Dmitry

  reply	other threads:[~2014-07-09 19:38 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 [this message]
2014-07-10  7:32       ` Hans de Goede
2014-07-10  8:45         ` Vojtech Pavlik
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=20140709193830.GE10364@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.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 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.