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 06:38:22 -0400 [thread overview]
Message-ID: <20170313103822.GL20039@beta.private.mielke.cc> (raw)
In-Reply-To: <20170313014641.GI20039@beta.private.mielke.cc>
[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.
I think I've misunderstood something about how to interpret bInterval. I'm now
suspecting that bInterval must be interpreted the new (mocro frame) way only if
the device is operating at least at high speed, and that, even if the device
advertizes itself as USB 2.0, bInterval must still be interpreted the old way
if the device is operating at full or low speed. Is that correct?
If the above is correct, how can we tell from usbfs which way to interpret
bInterval?
--
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 10:38 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 [this message]
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=20170313103822.GL20039@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®