I still don't understand how adding a filter driver to the stack fixes USB... :/
Either we have some essential USB code that depends on libusb functionality, but no libusb on the repo (which would be rather stupid), or adding the filter driver in the middle of the USB stack happens to hide a bug in one of the drivers (more likely). If it's the latter, it may be worth checking what the filter driver does differently than our USB drivers, in order to catch the issue it's "fixing". ;P On 20 May 2014 05:00, James Tabor <[email protected]> wrote: > It seems to work well, > > https://www.reactos.org/forum/viewtopic.php?f=4&t=13008&p=106242#p106242 > > > On Mon, May 19, 2014 at 5:56 AM, David Quintana (gigaherz) < > [email protected]> wrote: > >> As far as I understand, libusb is a means for usermode applications to >> attach themselves to an usb device, sending messages and receiving replies. >> >> What would the purpose be for libusb in the context of ReacOS? >> >> >> On 19 May 2014 12:38, Alexander Rechitskiy <[email protected]> wrote: >> >>> http://sourceforge.net/apps/trac/libusb-win32/wiki >>> >>> -- >>> Best regards, >>> Alexander Rechitskiy >>> >>> _______________________________________________ >>> Ros-dev mailing list >>> [email protected] >>> http://www.reactos.org/mailman/listinfo/ros-dev >>> >> >> >> _______________________________________________ >> Ros-dev mailing list >> [email protected] >> http://www.reactos.org/mailman/listinfo/ros-dev >> > > > _______________________________________________ > Ros-dev mailing list > [email protected] > http://www.reactos.org/mailman/listinfo/ros-dev >
_______________________________________________ Ros-dev mailing list [email protected] http://www.reactos.org/mailman/listinfo/ros-dev
