public inbox for linux-kernel@vger.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 20:41:57 +0200	[thread overview]
Message-ID: <20120704184157.GA272@polaris.bitmath.org> (raw)
In-Reply-To: <20120704083841.GA722@polaris.bitmath.org>

> 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...

Yep, that's it. On my system, something sets the L2CAP MTU to a
whopping 48 bytes, and the code below, from l2cap_core.c,

	switch (chan->mode) {
	case L2CAP_MODE_BASIC:
		/* If socket recv buffers overflows we drop data here
		 * which is *bad* because L2CAP has to be reliable.
		 * But we don't have any other choice. L2CAP doesn't
		 * provide flow control mechanism. */

		if (chan->imtu < skb->len)
			goto drop;

silently ignores packets larger than that value. Duh.

Henrik

      reply	other threads:[~2012-07-04 18:41 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
2012-07-04 18:41         ` Henrik Rydberg [this message]

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=20120704184157.GA272@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox