winusb host application & pipe policy

NTDEV
1

The WinUSB c# sample host program (downloaded from lvr.com) has a policy for setting the pipes…
[StructLayout(LayoutKind.Sequential)]
internal struct WINUSB_PIPE_INFORMATION
{
internal USBD_PIPE_TYPE PipeType;
internal Byte PipeId;
internal ushort MaximumPacketSize;
internal Byte Interval;
}

Does the host app really need to set the pipes policy since it is already done in the UMDF driver code to with ConfigureUsbPipes()?

Since I am porting over the fx2_driver testapp.c to handle the read/writes/ioctl, I am wondering why the testapp/dump executable doesn’t seem to set up a pipe policy like the WINUSB host program does???

2

The umdf driver does this. If you are using the umdf driver, forget about winusb and its interfaces when writing your app, none of it applies

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@mpr.com
Sent: Wednesday, December 01, 2010 6:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] winusb host application & pipe policy

The WinUSB c# sample host program (downloaded from lvr.com) has a policy for setting the pipes…
[StructLayout(LayoutKind.Sequential)]
internal struct WINUSB_PIPE_INFORMATION
{
internal USBD_PIPE_TYPE PipeType;
internal Byte PipeId;
internal ushort MaximumPacketSize;
internal Byte Interval;
}

Does the host app really need to set the pipes policy since it is already done in the UMDF driver code to with ConfigureUsbPipes()?

Since I am porting over the fx2_driver testapp.c to handle the read/writes/ioctl, I am wondering why the testapp/dump executable doesn’t seem to set up a pipe policy like the WINUSB host program does???

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer