public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Which USB device on which controller?
Date: Fri, 27 Feb 2009 09:55:26 -0600	[thread overview]
Message-ID: <49A80CEE.5000200@gmail.com> (raw)
In-Reply-To: <49bf44f10902270737s7cd41da0t734fdc00d5c67a73@mail.gmail.com>

Grant wrote:
>
> You seem to be right on here Dale.  usbview showed my printer
> connected to the 2.0 controller and a webcam connected to the 1.1
> controller, so I unplugged the printer and plugged the webcam into
> it's slot and it still showed up under 1.1.  So there doesn't appear
> to be any slot/controller correlation.
>
> This is a problem for me though.  My webcams can't both operate on the
> 1.1 controller at the same time due to the bandwidth limitation of the
> 1.1 controller.  I need them both on 2.0 or one on each controller,
> but they are always grabbed by the 1.1 controller.  Even worse, I
> disabled support for 1.1 in the kernel so only 2.0 was supported and
> the webcams didn't show up at all.  Could they be USB 1.1 only?
> Shouldn't a 1.1 device operate on a 2.0 controller?
>
> - Grant
>
>
>   


This is how I understand it.  Any 2.0 device should work with the older
1.0 version, just slower.  Backwards compatible.  However, like with my
camera, if the device is a version 1.0, it will only work in 1.0 mode. 
If you recently purchased this, you may want to exchange it and make
sure you get a 2.0 version.  That is if there is such a creature. 

The reason behind this is the chip inside the camera/webcam itself.  The
cable can cause this if it is not made for the new higher bandwidth or
is crappy but if the chip in there is the old 1.0 version, it can't go
any faster.

Another idea, you may be able to get a card to expand your USB ports and
see if that will help.  Each card has its own chip as well.  Put one
device on the card and one on the mobo port.  That way they are seen and
controlled by separate chips.  That should help with the bandwidth
problem at least.

Dale

:-)  :-) 



  parent reply	other threads:[~2009-02-27 15:55 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 [this message]
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
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=49A80CEE.5000200@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