qse drf wrote:
> I just installed the driver with Zadig. Yes there are two interfaces,
> interface 0 has a single endpoint and interface 1 has the two bulk end
> points. What confused me was that using libusbx I am able to use the bulk
> endpoints, but with the WinUSB API I can't.
I don't know how Zadig creates the INF file. Windows allows you to
write an INF file that claims the entire device:
%MyDeviceDesc% = install.section, USB\VID_11111&PID_2222
With that, you can get a handle to the other interfaces using
WinUSB_GetAssociatedInterface.
But Windows also allows you to write an INF that only claimes one interface:
%MyDeviceDesc% = install.section, USB\VID_11111&PID_2222&MI_00
or
%MyDeviceDesc% = install.section, USB\VID_11111&PID_2222&MI_01
If you use that option, then the system rewrites the descriptors so that
your driver doesn't even KNOW there is a second interface.
--
Tim Roberts, t...@probo.com
Providenza & Boekelheide, Inc.
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
