From: Tobias Philipp on
Hi(a)All,

Aim: App <-> UMDF USB Driver <-> ??? <-> USB PIC/FW

The PIC runs with the manufacturer driver. This driver is thrown away
and I would substitute it with an own UMDF driver.

Therefor I must install WinUSB driver as a filter driver, right?

At the upper Edge of the stack is the UMDF USB driver, right?

The problem @ the moment is how did the WinUSB driver knows that he is
used as a filter driver and should deliver requests from the pic to the
UMDF driver?

At the moment I read "How to Use WinUSB to Communicate with a USB
Device" but this is for the use as a function driver.

What must be delivered by the USB PIC/FW?

Best Regards
picdevice
From: Abhishek R [MSFT] on
The following whitepaper has some information on writing a UMDF driver for a
USB device. Note that it talks about both KMDF and UMDF. The UMDF parts
would be relevant to you.
http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/USB_WDF.doc

The OSR USB Fx2 sample in the WDK would also be worth looking at.
http://msdn.microsoft.com/en-us/library/dd163442.aspx

"Tobias Philipp" <fh-tphilipp(a)web.de> wrote in message
news:7s0kvsF7j2U1(a)mid.individual.net...
> Hi(a)All,
>
> Aim: App <-> UMDF USB Driver <-> ??? <-> USB PIC/FW
>
> The PIC runs with the manufacturer driver. This driver is thrown away and
> I would substitute it with an own UMDF driver.
>
> Therefor I must install WinUSB driver as a filter driver, right?
>
> At the upper Edge of the stack is the UMDF USB driver, right?
>
> The problem @ the moment is how did the WinUSB driver knows that he is
> used as a filter driver and should deliver requests from the pic to the
> UMDF driver?
>
> At the moment I read "How to Use WinUSB to Communicate with a USB Device"
> but this is for the use as a function driver.
>
> What must be delivered by the USB PIC/FW?
>
> Best Regards
> picdevice