linux-kernel - Re: [git pull] Input updates for 2.6.35-rc0

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 29 May 2010 08:27:17 +1000
From:	Peter Hutterer <peter.hutterer@...-t.net>
To:	Bastien Nocera <hadess@...ess.net>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Dave Airlie <airlied@...il.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Florian Ragwitz <rafl@...ian.org>,
	Arjan Opmeer <arjan@...eer.net>,
	Eric Piel <eric.piel@...mplin-utc.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-input@...r.kernel.org
Subject: Re: [git pull] Input updates for 2.6.35-rc0

On Fri, May 28, 2010 at 04:01:25PM +0100, Bastien Nocera wrote:
> > That Dell machine got a lot of bad reviews for its horribe touchpad, and I 
> > used to not understand why people disliked the touchpad so much - it 
> > didn't feel horrible to me. But now I wonder if Windows has the same 
> > logic, and reviewers - like me - hadn't realized to enable the tap 
> > feature.
> 
> On windows, it's basically as horrible as you suggested if you don't
> install the elantech drivers.
> 
> For the default GNOME configuration, we could certainly switch it again,
> but we would break people with older laptops.
> 
> Seeing as we already know if there's physical buttons, we would just
> need to know whether the physical buttons are embedded in the touchpad
> like on yours. Then we could make an informed decision about the
> defaults.
> 
> I'm sure that Peter would love the challenge of exporting that to the
> desktops :)

Yeah. exciting...
At the moment we rely on udev to tag the device based on the the dmi product
name. Unless I've missed something else, this is the _only_ thing we can go
on. The touchpad hardware itself looks sane and even the driver doesn't know
that this touchpad is crap, it simply applies an option to disable part of
the touchpad for movements because that's what our xorg.conf.d snippets say.
I'd love to have an EVIOISTHISDEVICEONCRACK ioctl, but for now we have to
work around it.

For clients, well, I just don't know yet how to export this.

Cheers,
  Peter
--
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/