usbfn client driver
|
Prev: How to soft-reset after installation on Windows mobile
Next: How to override Home Key in Windows Mobile
From: mikelan on 22 Dec 2009 02:10 Hi In my Windows Mobile, bsp_usbfn.dll(usbfn.dll) is the USB function controller driver. It's registered in \Drivers\BuiltIn\Usbfn, and loaded when system is booted. call CreateBusAccessHandle(), and then call GetParentDeviceInfo() I can get some information about usbfn.dll ddi.dwSize:1584 ddi.hDevice:383680 ddi.hParentDevice:213120 ddi.szDeviceKey: Drivers\BuiltIn\Usbfn ddi.szLegacyName: UFN1: ddi.szDeviceName: $device\UFN1 ddi.szBusName: $bus\BuiltIn_0_1_0 I want to get the MDD function table UFN_FUNCTIONS. Could you please give me a little advice? thanks in advance mike
From: mikelan on 22 Dec 2009 03:54 The following table shows the functions that USB function client drivers implement. lpRegisterDevice lpStart .... lpSendControlStatusHandshake -- from MSDN but on the contrary UfnInitializeInterface in the source code E:\WINCE600\PUBLIC\COMMON\OAK\DRIVERS\USBFN\ shows that usb function client drivers get UFN_FUNCTIONS from ufn bus driver's mdd part, not put UFN_FUNCTIONS into ufn bus driver's mdd part. put into mdd or get from mdd? could anyone give me some advice, which one is correct? mike young "mikelan" <yangjie(a)posat.net> д����Ϣ����:%233%233gXtgKHA.1824(a)TK2MSFTNGP04.phx.gbl... > Hi > > In my Windows Mobile, bsp_usbfn.dll(usbfn.dll) is the USB > function controller driver. It's registered in > \Drivers\BuiltIn\Usbfn, and loaded when system is booted. > > call CreateBusAccessHandle(), and then call GetParentDeviceInfo() > I can get some information about usbfn.dll > > ddi.dwSize:1584 > ddi.hDevice:383680 > ddi.hParentDevice:213120 > ddi.szDeviceKey: Drivers\BuiltIn\Usbfn > ddi.szLegacyName: UFN1: > ddi.szDeviceName: $device\UFN1 > ddi.szBusName: $bus\BuiltIn_0_1_0 > > > I want to get the MDD function table UFN_FUNCTIONS. > Could you please give me a little advice? > > thanks in advance > > mike > >
From: Robert Clacton on 23 Dec 2009 22:02
You should call UfnInitializeInterface get these UFN_FUNCTIONS. "mikelan" <yangjie(a)posat.net> д����Ϣ����:ugPISRugKHA.5460(a)TK2MSFTNGP06.phx.gbl... > The following table shows the functions that USB function client drivers > implement. > > lpRegisterDevice > lpStart > ... > lpSendControlStatusHandshake > > -- from MSDN > > > but on the contrary UfnInitializeInterface in the source code > E:\WINCE600\PUBLIC\COMMON\OAK\DRIVERS\USBFN\ > shows that usb function client drivers get UFN_FUNCTIONS from ufn bus > driver's mdd part, not put UFN_FUNCTIONS into ufn bus driver's mdd part. > > > put into mdd or get from mdd? could anyone give me some advice, which one > is correct? > > mike young > > |