mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christopher Montgomery" <xiphmont@gmail.com>
To: "Ian Stirling" <tandra@mauve.plus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] USB bandwidth enforcement troubles.
Date: Sat, 22 Jul 2006 12:58:21 -0400	[thread overview]
Message-ID: <806dafc20607220958n1f5d0c88s6e64d1771585ea69@mail.gmail.com> (raw)
In-Reply-To: <44C212A8.7050806@mauve.plus.com>

Nothing is simple in USB, although 1.1 is alot easier than 2.0 :-)

The logs, unfortunately, don't tell much.  But the short answer is
probably 'don't use USB bandwidth enforcement'.  If the bandwidth
request it is reporting is accurate, the kernel is correctly rejecting
the request.  But, I suspect strongly either the kernel is
miscalculating or the headset is vastly overreporting its needs.
991us in a FS frame would indeed be too much to schedule, but no
headset would ever have cause to use that kind of bandwidth.

Monty

      reply	other threads:[~2006-07-22 16:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-22 11:57 Ian Stirling
2006-07-22 16:58 ` Christopher Montgomery [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=806dafc20607220958n1f5d0c88s6e64d1771585ea69@mail.gmail.com \
    --to=xiphmont@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tandra@mauve.plus.com \
    /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®