On Mon, Oct 1, 2012 at 5:24 AM, Pete Batard <p...@akeo.ie> wrote: >>Of course, a nice graphical >> presentation of the Windows driver layering would be very welcome :) > > 1. With libusbK.dll available > > libusbx > | > V > libusbK.dll > | > +--------------------+---------------------+ > | | | > V V V > WinUSB.dll libusb-win32.dll libusbK driver > | | (libusbk.sys) > V V > WinUSB driver libusb-win32 driver > (WinUSB.sys) (libusb0.sys) > > NB: libusb-win32.dll is really named libusb0.dll, but that doesn't > really matter for this illustration
One minor issue, libusb0.dll is not used for libusbK.dll, libusbk.dll directly talked to libusb0.sys, just like it directly talks to libusbk.sys. > Oh, for the sake of completion, note that the libusbK driver actually > installs both the libusbK and libusb-win32 DLLs, which brings me to a > question to Xiaofan: > > Should we expect people not to install libusb-win32 using a libwdi > derivative? The inf-wizard from libusb-win32 release does use libwdi but it does not bundle libusbk.dll. libusbK's inf-wizard (MFC based) does bundle libusbk.dll and libusb0.dll for both libusb0.sys and libusbk.sys since libusbk.dll and libusb0.dll work with both libusb0.sys and libusbk.sys. libusbk.dll will work with winusb but not libusb0.dll. > Right now, the only reason I see to keep the libusb-win32 DLL install in > K.inf is if we expect someone to just drop a libusb0.sys, which I don't > expect to be a common occurrence, and even then, I would assume that > someone producing their own inf would take care to add libusb0.dll. libusb0.dll is for the libusb-win32 API which is a superset of libusb-0.1 API. For the purpose of libusbx, Zadig can remove the libusb0.dll. But for libusbK project, we will need to keep the backward compatibility with libusb-win32 API (libusb0.dll). > Or does the libusbK DLL require access to libusb-win32 API functions, > regardless of whether the driver is present? > I must admit I can't remember what made you guys want to have a K.inf > that installed libusb-win32.dll, and since we're cleaning the DLL > dependencies, we might want to sort both sides. libusbk.sys can act as a drop-in replacement of libusb0.sys (with a few limitations) and we want to support libusb-win32 API user (libusb0.dll user). -- Xiaofan ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
