In the current libusbx implementation, the topology information is important
since it is part of the topology API.
BTW, have you been able to update your xHCI driver to see if your original
issue goes away? That is a better solution IMHO.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/137#issuecomment-24861296
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13.
http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
