public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Hutterer <peter.hutterer@who-t.net>
To: Bastien Nocera <hadess@hadess.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Dave Airlie <airlied@gmail.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Florian Ragwitz <rafl@debian.org>,
	Arjan Opmeer <arjan@opmeer.net>,
	Eric Piel <eric.piel@tremplin-utc.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org
Subject: Re: [git pull] Input updates for 2.6.35-rc0
Date: Sat, 29 May 2010 08:27:17 +1000	[thread overview]
Message-ID: <20100528222717.GB28502@barra> (raw)
In-Reply-To: <1275058885.31676.7166.camel@localhost.localdomain>

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

  reply	other threads:[~2010-05-28 22:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 16:52 [git pull] Input updates for 2.6.35-rc0 Dmitry Torokhov
2010-05-28  1:53 ` Linus Torvalds
2010-05-28  2:46   ` Dmitry Torokhov
2010-05-28  4:06     ` Linus Torvalds
2010-05-28  2:56   ` Dave Airlie
2010-05-28  4:12     ` Linus Torvalds
2010-05-28  5:07       ` Dmitry Torokhov
2010-05-28 14:23         ` Linus Torvalds
2010-05-28  5:44       ` Dave Airlie
2010-05-28  6:19         ` Peter Hutterer
2010-05-28 14:28           ` Linus Torvalds
2010-05-28 15:01             ` Bastien Nocera
2010-05-28 22:27               ` Peter Hutterer [this message]
2010-05-28  7:23       ` Éric Piel
  -- strict thread matches above, loose matches on Subject: below --
2010-05-27 16:14 Dmitry Torokhov

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=20100528222717.GB28502@barra \
    --to=peter.hutterer@who-t.net \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@opmeer.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=eric.piel@tremplin-utc.net \
    --cc=hadess@hadess.net \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafl@debian.org \
    --cc=torvalds@linux-foundation.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