Partager via


USB Function Controller Driver Migration (Windows Embedded CE 6.0)

1/6/2010

Architecturally, a USB function client driver is above a USB function controller driver. A USB function client driver interfaces with a USB function controller driver through the USB function controller driver's hardware independent MDD. The USB function controller driver's MDD and all USB function client drivers are hardware platform independent. Multiple USB function client drivers interface with the same USB function controller driver. Each client interfaces with the USB function controller driver through the USB function controller driver's MDD. Along with the MDD, a USB function controller driver is also comprised of a PDD, which is architecturally below the MDD. The PDD interfaces directly with the USB function controller hardware.

Microsoft provides hardware platform independent USB function client drivers for RNDIS, serial, and storage. They are in %_WINCEROOT%\Public\Common\OAK\Drivers\USBFN\Class. The MDD for these USB function client drivers is in %_WINCEROOT%\Public\Common\OAK\Drivers\USBFN\Controller\MDD. For more information, see USB Function Client Drivers.

Generally, to port a USB function controller driver, only modify the PDD. Different PDDs may require different modifications. Microsoft provides PDDs for various chipsets:

  • %_WINCEROOT%\Platform\Common\Src\SOC\PXA27X_MS_v1\USBFN
  • %_WINCEROOT%\Platform\Deviceemulator\Src\Drivers\USB\Function
  • %_WINCEROOT%\Public\Common\OAK\Drivers\USBFN\Controller\Net2280

Drivers implemented for specific USB function controllers are in %_WINCEROOT%\Platform\Common\Src\SOC subdirectories. The modifications to make to these drivers depend on the hardware platform to which you are porting the driver. Hardware platform independent drivers are in %_WINCEROOT%\Public\Common\OAK\Drivers.

In This Section

See Also

Concepts

USB Function Controller Drivers