From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Which USB device on which controller?
Date: Fri, 27 Feb 2009 15:24:02 -0600 [thread overview]
Message-ID: <49A859F2.3060507@gmail.com> (raw)
In-Reply-To: <49bf44f10902271221k30134a9fg907bc477dfc3683@mail.gmail.com>
Grant wrote:
>>>> I'm looking at the box of one of the webcams and it says "USB 2.0
>>>> compatible".
>>>>
>>>>
>>> A USB 1.1 device _is_ "USB 2.0 compatible" because a USB 2.0
>>> will slow down and run at 1.1 speed. Does the device say it's
>>> "high speed" USB? "USB 2.0 compatible" generally means it's a
>>> USB 1.1 device.
>>>
>>>
>>>
>>>> It's not a cable problem because the cable is built right into
>>>> the webcam. I'm not trying to get the webcam to go faster
>>>> back and forth to the controller, I just need to make sure I
>>>> don't have both webcams on the same OHCI (1.1) USB controller.
>>>> I would think buying a USB expansion card would work, but I
>>>> have an EHCI (2.0) controller on this system and a second OHCI
>>>> (1.1) controller.
>>>>
>>>> Does anyone have any idea on this. It really doesn't make sense.
>>>>
>>>>
>>> Sounds like it's a 1.1 device to me.
>>>
>>>
>>>
>> Yep, that's what it sounds like to me too.
>>
>> Dale
>>
>
> But that's OK isn't it? I don't need 2.0 speeds between each webcam
> and the controller, I just need the increased overall bandwidth of a
> 2.0 controller so one of the 1.1 webcams doesn't use all of it. I get
> the feeling I have a misconception somewhere along the line here.
> Could someone straighten me out?
>
> - Grant
>
>
>
If the camera is using USB version 1.0, or the slow connection, it won't
ever work as a 2.0. It is just not capable of that. It would be like
me wanting my old dial-up modem to connect to my ISP at 256K/s. It
can't do that because it was not built to do that or has the hardware to
do it either. Not to mention that my ISP would not be happy either.
I suspect that sort of like my IDE bus, when I have a old drive on the
same cable as a fast one, it is slower because of all the negotiating
that goes on between the different devices. I may be wrong but I don't
think you are going to be able to get two cameras to work unless they
are both USB 2.0 or on a separate chip such as a expansion card.
The camera is your limiting factor from what I understand.
Dale
:-) :-)
next prev parent reply other threads:[~2009-02-27 21:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 3:34 [gentoo-user] Which USB device on which controller? Grant
2009-02-27 3:53 ` Dale
2009-02-27 5:42 ` Grant
2009-02-27 6:08 ` [gentoo-user] " Grant Edwards
2009-02-27 6:43 ` [gentoo-user] " Dale
2009-02-27 15:37 ` Grant
2009-02-27 15:47 ` Alan McKinnon
2009-02-27 16:53 ` Grant
2009-02-27 15:55 ` Dale
2009-02-27 17:00 ` Grant
2009-02-27 17:26 ` [gentoo-user] " Grant Edwards
2009-02-27 17:30 ` Dale
2009-02-27 20:21 ` Grant
2009-02-27 21:19 ` Joshua Murphy
2009-02-27 21:24 ` Dale [this message]
2009-02-27 23:34 ` Mark Knecht
2009-02-28 5:24 ` Grant Edwards
2009-02-28 14:54 ` Grant
2009-02-28 18:30 ` Mark Knecht
2009-03-01 18:41 ` Grant
2009-03-01 19:29 ` Grant
2009-02-28 20:09 ` Neil Bothwick
2009-02-27 12:50 ` [gentoo-user] " Mark Knecht
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=49A859F2.3060507@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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