Date: Sat, 23 Jul 2011 18:53:46 +0200 From: Peer Stritzinger <peerst@gmail.com> To: Hans Petter Selasky <hselasky@c2i.net> Cc: freebsd-usb <freebsd-usb@freebsd.org> Subject: Re: Powercycling USB device on hub Message-ID: <CA%2BervzZ790PH4TTE%2BNf7cjdfpmu60WPS94qAbVURNEBir7Z8QQ@mail.gmail.com> In-Reply-To: <201107231755.23755.hselasky@c2i.net> References: <CA%2BervzZXRTHk6GWSy0HMELaANdwYia4ddQ1pX=tCrPx73pqMtg@mail.gmail.com> <201107231717.34403.hselasky@c2i.net> <CA%2BervzbnXmwpKpi=craQVM8O13=8if8gKaxPLot1etDPRSREHA@mail.gmail.com> <201107231755.23755.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 23, 2011 at 5:55 PM, Hans Petter Selasky <hselasky@c2i.net> wro=
te:
>> Since power-cycling needs to reset the HUB I now have the problem to
>> find out on which HUB in the system my device hangs.
>>
>> There are two HUB's on the same root HUB and I don't want to
>> power-cycle all devices. =A0Is there a way to learn the physical
>> structure of a USB bus?
>
> devinfo
>
> Address 1 is always the root HUB.
Tried this already but it only shows the hubs but none of my devices
because they have no driver (custom built USB devices, only talk to
them via libusb).
e.g.
usbus3
uhub3
uhub4 pnpinfo vendor=3D0x0424 product=3D0x2514 devclass=3D0x0=
9
devsubclass=3D0x00 sernum=3D"" release=3D0x0bb3 intclass=3D0x09
intsubclass=3D0x00 at port=3D7 interface=3D0
uhub5 pnpinfo vendor=3D0x0424 product=3D0x2514 devclass=3D0x0=
9
devsubclass=3D0x00 sernum=3D"" release=3D0x0bb3 intclass=3D0x09
intsubclass=3D0x00 at port=3D8 interface=3D0
There is one of the devices attached either to uhub4 or uhub5 (visible
in usbconfig) but nothing shown in devinfo (even with -v).
-- Peer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BervzZ790PH4TTE%2BNf7cjdfpmu60WPS94qAbVURNEBir7Z8QQ>