All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Henrik Rydberg" <rydberg@euromail.se>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: Chase Douglas <chase.douglas@canonical.com>,
	Yufeng Shen <miletus@chromium.org>,
	linux-input@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>,
	linux-kernel@vger.kernel.org,
	Andrew de los Reyes <adlr@chromium.org>
Subject: Re: [PATCH 1/2 v2] HID: magicmouse: Removing report_touches switch
Date: Wed, 4 Jul 2012 10:38:41 +0200	[thread overview]
Message-ID: <20120704083841.GA722@polaris.bitmath.org> (raw)
In-Reply-To: <CAGS+omDHQkWdmETOwaDu3nkAQEhJeNkLDdDmF+4N=XDTO6+FWg@mail.gmail.com>

Hi Daniel,

> What Bluetooth host controller are you using?

It is a USB device (0a5c:4500), part of a BCM2046 sitting in a MacBook
Air. The driver is btusb.

> Which part are you testing (Magic TP or mouse)?

Magic trackpad.

> I've been trying to test these patches on a Magic Trackpad using two
> computers, with two different ath3k parts.
> On one of them, the BT communication freezes immediately after the
> first report with 3 fingers.
> On the other, it reports all 10 fingers, just fine.

Interesting. Clearly not a HID problem, then.

> The only difference I can tell is the version of the Atheros Bluetooth chip.
> 
> What does your freeze look like?

The input events stop coming when I have more than four fingers on the
pad, but they start again if I remove the excess fingers. As if the
transport layer chokes on messages longer than some value...

Thanks,
Henrik

  reply	other threads:[~2012-07-04  8:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 18:53 [PATCH 1/2 v2] HID: magicmouse: Removing report_touches switch Yufeng Shen
2012-07-03 20:27 ` Chase Douglas
2012-07-04  7:40   ` Henrik Rydberg
2012-07-04  7:49     ` Daniel Kurtz
2012-07-04  8:38       ` Henrik Rydberg [this message]
2012-07-04 18:41         ` Henrik Rydberg

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=20120704083841.GA722@polaris.bitmath.org \
    --to=rydberg@euromail.se \
    --cc=adlr@chromium.org \
    --cc=chase.douglas@canonical.com \
    --cc=djkurtz@chromium.org \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miletus@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.