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: Mon, 13 Mar 2017 22:20:01 -0400 [thread overview]
Message-ID: <20170314022001.GR20039@beta.private.mielke.cc> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1703132129450.16895-100000@netrider.rowland.org>
Thank you for your very helpful answer. I really do appreciate it.
It's possible that this device is using high speed because it offers a feature
to transfer its internal clipboard to the host, and it allows that clipboard to
contain lots of data. Interestingly, though, hidden within a usage note, they
do observe that, so far, they've been unable to achieve a transfer speed faster
than 5,000 characters in seven minutes. It looks to me like this is exactly due
to their incorrect setting of bInterval. :-) I've sent them a note about it.
--
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-14 2:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 20:10 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
2017-03-13 10:38 ` Dave Mielke
2017-03-14 1:43 ` Alan Stern
2017-03-14 2:20 ` Dave Mielke [this message]
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=20170314022001.GR20039@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®