public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <sonne@debian.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Adrian Bunk <bunk@stusta.de>,
	olh@suse.de, Jiri Slaby <jirislaby@gmail.com>
Subject: Re: [PATCH] mouse button 1 emulation for mac_hid
Date: Mon, 16 Nov 2009 18:11:51 +0100	[thread overview]
Message-ID: <1258391511.3419.131.camel@no> (raw)
In-Reply-To: <20091116170543.GB24026@core.coreip.homeip.net>

[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]

On Mon, 2009-11-16 at 09:05 -0800, Dmitry Torokhov wrote:
> On Mon, Nov 16, 2009 at 01:59:37PM +0100, Jiri Kosina wrote:
> > On Fri, 13 Nov 2009, Dmitry Torokhov wrote:
> > 
> > > > I am not sure what the future of mac_hid is (the source says will be
> > > > removed, but since 9 years). In case it stays in kernel the attached
> > > > patch adds support for mouse button 1 emulation. If this driver stays in
> > > > the kernel I would also suggest to rename it - it is not mac specific (I
> > > > am using this on a netbook).
> > > > 
> > > > Rationale? Broken touchpads, within linux unsupported (multi-)touchpads
> > > > where click and hold + moving the mouse does not work (yet?).
> > > 
> > > I would rather fix the touchpads so they work properly than pile more
> > > quirks in kernel.
> > 
> > Hi Dmitry,
> > 
> > in exactly what way are you planning to "fix the touchpads"?
> > 
> 
> Hi Jiri,
> 
> It would be helpful to know which ones are currently. Obviously we can't
> help with physically broken ones but I don't believe it is kernel's task
> to deal with physically broken hardware. The ones that are not
> physically broken - PS/2 should have fairly decent hardware emulation
> mode (at least all I tried supported tap and trag while working as
> regular PS/2 mouse) - so that can be used while we figuring out native
> protocol. USB - appletouch, bcm - are there any issues at the moment?

Ignoring broken hardware, there is the problem or feature that some
touchpads have the mouse *under the touchpad*. So when you click there
and want to move the mouse - well good luck. Of course this is something
that needs to be ultimately fixed in the synaptics xorg driver.

Soeren
-- 
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-11-16 17:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 10:28 [PATCH] mouse button 1 emulation for mac_hid Soeren Sonnenburg
2009-11-14  5:42 ` Dmitry Torokhov
2009-11-14 10:31   ` Soeren Sonnenburg
2009-11-16 12:59   ` Jiri Kosina
2009-11-16 17:05     ` Dmitry Torokhov
2009-11-16 17:11       ` Soeren Sonnenburg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-31 10:57 [PATCH] mouse button #1 " Soeren Sonnenburg

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=1258391511.3419.131.camel@no \
    --to=sonne@debian.org \
    --cc=bunk@stusta.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jirislaby@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olh@suse.de \
    --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