From: Dave Mielke <dave@mielke.cc>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, kevin.derome@epitech.eu,
clause.andreabush@gmail.com, mengualjeanphi@free.fr
Subject: Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
Date: Sun, 12 Mar 2017 21:46:41 -0400 [thread overview]
Message-ID: <20170313014641.GI20039@beta.private.mielke.cc> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1703122139020.30930-100000@netrider.rowland.org>
[quoted lines by Alan Stern on 2017/03/12 at 21:40 -0400]
>No, I was wondering why an HID device would run at high speed. Both
>you and Samuel implied that this was because it was a USB-2 device.
>But that is not an adequate answer, because it is perfectly valid for a
>USB-2 device to run at full speed.
What should we look at to find out what speed it wants to operate at? We didn't
look into it becuaase the real problem, from our perspective, was that the 64ms
interval was being honoured by the host when it should be the 10ms as is
literally in the endpoint descriptor. Our assumption was that since it says
it's USB 2.0 then bInterval must be intterpreted in light of that regardless of
the actual speed used for communication.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/
EMail: Dave@Mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
next prev parent reply other threads:[~2017-03-13 1:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 20:10 [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk Samuel Thibault
2017-03-12 21:18 ` Alan Stern
2017-03-12 21:42 ` Dave Mielke
2017-03-13 1:31 ` Alan Stern
2017-03-13 1:36 ` Dave Mielke
2017-03-13 1:40 ` Alan Stern
2017-03-13 1:46 ` Dave Mielke [this message]
2017-03-13 10:38 ` Dave Mielke
2017-03-14 1:43 ` Alan Stern
2017-03-14 2:20 ` Dave Mielke
2017-03-14 8:45 ` Samuel Thibault
2017-03-13 7:05 ` Samuel Thibault
2017-03-14 1:44 ` Alan Stern
2017-03-12 21:47 ` Samuel Thibault
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=20170313014641.GI20039@beta.private.mielke.cc \
--to=dave@mielke.cc \
--cc=clause.andreabush@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kevin.derome@epitech.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mengualjeanphi@free.fr \
--cc=samuel.thibault@ens-lyon.org \
--cc=stern@rowland.harvard.edu \
/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.