Linux Input/HID development
 help / color / mirror / Atom feed
From: Henrik Rydberg <rydberg@euromail.se>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	robfitz@273k.net, akpm@osdl.org, Vojtech Pavlik <vojtech@suse.cz>,
	dmonakhov@openvz.org
Subject: Re: [PATCH] hid: wellspring device quirks
Date: Tue, 22 Jul 2008 15:31:42 +0200	[thread overview]
Message-ID: <4885E13E.1010607@euromail.se> (raw)
In-Reply-To: <alpine.LNX.1.10.0807221504380.3037@jikos.suse.cz>

Jiri Kosina wrote:
> On Sun, 13 Jul 2008, Henrik Rydberg wrote:
> 
>> This patch adds the HID_QUIRK_IGNORE_MOUSE quirk for the Apple USB
>> multitouch devices based on BCM5974, aka Wellspring. These devices
>> will instead be picked up by the new bcm5974 driver.
> 
> Hi Henrik,
> 
> is the mouse not working at all with standard HID driver?
> 

Yes, it is working out-of-the-box, only poorly.

> I'd prefer to postpone merging this patch until bcm5974 hits mainline if
> the device works in a limited way with standard HID driver, so that we
> don't introduce regression.
> 

Absolutely, this patch should be applied together with the bcm5974 driver,
or not be applied. The driver patch is here:

http://userweb.kernel.org/~akpm/mmotm/broken-out/input-bcm5974-055-smoother-motion-irq-simplification.patch

> If the device doesn't work with HID driver at all though, it is probably
> perfectly fine to merge it right away. Please let me know, I have no
> knowledge about this particular device.

It is fine to leave it, but I would of course prefer to have the driver included together with this patch.

Thanks!
Henrik Rydberg


  reply	other threads:[~2008-07-22 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-13 15:34 [PATCH] hid: wellspring device quirks Henrik Rydberg
2008-07-22 13:08 ` Jiri Kosina
2008-07-22 13:31   ` Henrik Rydberg [this message]
2008-07-22 13:54     ` Dmitry Torokhov
2008-07-22 13:59       ` Jiri Kosina

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=4885E13E.1010607@euromail.se \
    --to=rydberg@euromail.se \
    --cc=akpm@osdl.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dmonakhov@openvz.org \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robfitz@273k.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox