From: Robert Hancock <hancockr@shaw.ca>
To: Michael Bueker <m.bueker@berlin.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OHCI: USB webcam works, but not on USB Hub
Date: Tue, 03 Apr 2007 08:33:39 -0600 [thread overview]
Message-ID: <461265C3.4060900@shaw.ca> (raw)
In-Reply-To: <fa.R4OJEk76c3blNmi9oUs1xDRZGis@ifi.uio.no>
Michael Bueker wrote:
> [please CC me on this thread]
>
> Hi everyone,
>
> My system has an nForce4 motherboard with an OHCI USB controller.
>
> I'm using a USB Webcam with the gspca driver (from
> http://mxhaard.free.fr/download.html), which has been working fine with the
> latest kernels.
>
> Today, I connected a USB Hub and the camera to it, after which it stopped
> working with the error message:
>> ERROR opening V4L interface
>> : Function not implemented
> However, it works fine when not connected to the Hub, but a motherboard's own
> USB port. The Hub also works fine with any other USB device.
>
> I googled around for a solution and found one for an older version of my
> driver, where the (apparently very ugly) fix was to manually set a fixed
> bandwidth for the USB device, instead of using a somehow other determined
> value. See this posting for a more elaborate description:
> http://lists.zerezo.com/spca50x-devs/msg00664.html
>
> Now, I'm writing to this list because one of the followups to that post
> (http://lists.zerezo.com/spca50x-devs/msg00665.html) states that this is due
> to a problem with the Linux USB layer:
>> pls file a bug "ohci driver can't handle low+fullspeed devices on the same
>> root hub" to linux usb devel list.
>
> That's about all I can tell you for now. I've attached two outputs of
> lsusb -vv, one with the hub attached, with the camera and a USB stick
> connected (notice the error message), and one without the hub and the
> camera connected directly (which is the setup where it works fine).
I looked into this at one point previously with spca5xx. Certainly in my
case it was no fault of the kernel. The isochronous descriptor that the
driver was deciding to use required so much bandwidth that it couldn't
be accomodated if anything else was using timeslots on the bus - even a
USB keyboard/mouse on the same hub would prevent it from getting enough
bandwidth.
Essentially the driver should fallback to a lower-bandwidth descriptor
if the one it tries to use fails rather than just bailing out.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-04-03 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.R4OJEk76c3blNmi9oUs1xDRZGis@ifi.uio.no>
2007-04-03 14:33 ` Robert Hancock [this message]
2007-04-03 14:41 OHCI: USB webcam works, but not on USB Hub Nicolas Mailhot
2007-04-03 15:22 ` Kok, Auke
2007-04-03 15:48 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2007-04-03 12:02 Michael Bueker
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=461265C3.4060900@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=m.bueker@berlin.de \
/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