lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 11 Oct 2010 09:28:10 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Henrik Rydberg <rydberg@...omail.se>,
	Chase Douglas <chase.douglas@...onical.com>,
	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] Input: synaptics - multitouch and multifinger support

At Sun, 10 Oct 2010 13:59:32 -0700,
Dmitry Torokhov wrote:
> 
> On Sun, Oct 10, 2010 at 09:49:45AM +0200, Henrik Rydberg wrote:
> > Takashi, Chase,
> > 
> > talk about Heinz effect. :-)
> > 
> > Rather than taking any of the patches, I was wondering if we could get a single
> > patch including all the later findings and considerations on what devices should
> > have the multitouch mode. Also, unless there is a really really good reason for
> > it, without kernel parameters. After all, these patches should only add new
> > functionality without regressions.
> 
> Yes, I think we should limit number of module options (and even more so
> Kconfig options). I believe that either MT support is ready for prime-time
> and then it should be enabled unconditionally, or it is not ready and
> should be kept as patches. his also means that we should not introduce
> regressions in ST (even when emulated in MT mode).

Right, but it's pretty hard to know whether it works really for all
machines, simply because the current MT-detection is nothing but a
pure guess work.  As mentioned in another mail, there are devices that
have no this bit but reports multi-finger detections without
tracking.  So, there are definitely other things to be checked.

Thus, I'm inclined to add a module option, at least, for *disabling*
MT for non-working machines.  Also, another question is whether it's
safe to enable MT even for user-space that don't understand MT.


Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ