Grant wrote:
> My system seems to have 2 USB controllers, one 1.1 controller (OHCI)
> and one 2.0 controller (EHCI):
>
> 00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev
> a3) (prog-if 10 [OHCI])
>       Subsystem: Micro-Star International Co., Ltd. Device 7309
>       Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21
>       Memory at dfe7f000 (32-bit, non-prefetchable) [size=4K]
>       Capabilities: [44] Power Management version 2
>       Kernel driver in use: ohci_hcd
>
> 00:02.1 USB Controller: nVidia Corporation MCP61 USB Controller (rev
> a3) (prog-if 20 [EHCI])
>       Subsystem: Micro-Star International Co., Ltd. Device 7309
>       Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22
>       Memory at dfe7ec00 (32-bit, non-prefetchable) [size=256]
>       Capabilities: [44] Debug port: BAR=1 offset=0098
>       Capabilities: [80] Power Management version 2
>       Kernel driver in use: ehci_hcd
>
> I have 2 Philips USB webcams attached to this system and controlled by
> media-video/motion.  One of the webcams is not functioning, and I'm
> supposed to make sure I don't have both of them attached to the USB
> 1.1 controller.  How can I do that?  I have:
>
> # lsusb
> Bus 001 Device 003: ID 04f9:002a Brother Industries, Ltd
> Bus 001 Device 001: ID 1d6b:0002
> Bus 002 Device 003: ID 0471:0329 Philips
> Bus 002 Device 002: ID 0471:0329 Philips
> Bus 002 Device 001: ID 1d6b:0001
>
> Is there any way to find out?
>
> - Grant
>
>
>   


I !think! mine has that too.  This is the usb part of my config:

r...@smoker / # cat /usr/src/linux/.config | grep USB | grep =y
CONFIG_USB_HID=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_ACM=y
CONFIG_USB_PRINTER=y
CONFIG_USB_STORAGE=y
r...@smoker / #   

With mine, it tries 2.0 first then goes to the first version.  My
printer is 2.0 but my camera is the old version, or maybe it is the
other way around.  I got a memory stick that connects 2.0 to.  Anyway,
that works here and it may work for you.

Dale

:-)  :-) 

Reply via email to