linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chase Douglas <chase.douglas@canonical.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input <linux-input@vger.kernel.org>,
	Michael Poole <mdpoole@troilus.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Alan Ott <alan@signal11.us>
Subject: Re: 35022: hid-magicmouse broken
Date: Tue, 17 May 2011 15:14:27 -0400	[thread overview]
Message-ID: <4DD2C913.4000403@canonical.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1105171448230.28291@pobox.suse.cz>

On 05/17/2011 08:56 AM, Jiri Kosina wrote:
> On Tue, 17 May 2011, Chase Douglas wrote:
> 
>> Hi Jiri,
>>
>> I've received a few emails about the magicmouse driver being broken on
>> 2.6.39:
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=35022
>>
>> It seems hid_output_raw_report() is returning a different (incorrect?)
>> value than in the past. Do you know what might be going on?
> 
> So we are getting EIO from the transport-level _raw callback.
> 
> Hmm, commit 0825411ade seems like a suspect here. Might be possible that 
> magicmouse doesn't send ACK back, right?
> 
> Could you please try reverting that commit and re-test?

Yes, reverting that commit makes it work.

I'm just speculating here, based on commit message names and what you've
said, that the magicmouse is not protocol compliant because it is not
sending an ACK back? What do you think we should do in the driver?
Should we ignore the return, or should we look specifically for EIO?
(neither sounds very good to me, so I'm hoping you have a better
solution :).

Thanks!

-- Chase

  reply	other threads:[~2011-05-17 19:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 12:40 35022: hid-magicmouse broken Chase Douglas
2011-05-17 12:56 ` Jiri Kosina
2011-05-17 19:14   ` Chase Douglas [this message]
2011-05-19 11:59     ` Jiri Kosina
2011-05-19 13:13       ` Chase Douglas
2011-05-19 14:54         ` Jiri Kosina
2011-05-19 15:40           ` Chase Douglas
2011-05-19 16:03             ` Jiri Kosina
2011-05-19 18:03               ` Chase Douglas
2011-05-20  8:28                 ` Jiri Kosina
2011-05-20 13:04                   ` Chase Douglas
2011-05-23  9:04                     ` 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=4DD2C913.4000403@canonical.com \
    --to=chase.douglas@canonical.com \
    --cc=alan@signal11.us \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=mdpoole@troilus.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;
as well as URLs for NNTP newsgroup(s).