Mobile Apps - A confusion with merging 2 NDIS miniport driver
Asked By vincent.tsai
07-Nov-09 03:36 AM
Hi:
i had a BSP MIPSII, CE5 with MAC driver include miniport driver.
i want to merge a vendor's wifi driver into the BSP .This wifi driver also
include miniport driver.
these 2 miniport driver have the same function name but different contents,
for example,MiniportInitialize MiniportISR .
For merging these 2 dll into my BSP, should i merge the same name functions
into one(only one)function name in the BSP?
or they can be as originally in different DLL with the same function name?
hope to get the clearness of this confusion.
any comment would be appreciated.
Best Regards.
vincent tsai
MiniportISR
(1)
DLLs
(1)
MiniportInitialize
(1)
Clearness
(1)
Registry
(1)
Miniport
(1)
Adapters
(1)
Vincent
(1)
Paul G. Tobey [eMVP] replied to vincent.tsai
You do not have to do anything. You've got two adapters; they should have
two drivers. The BSP is just a collection of stuff, NOT A SINGLE DLL THAT
HAS TO INCLUDE ALL OF THE CODE THAT SUPPORTS YOUR BOARD. Just use the DLLs
as they are with suitable registry entries.
Paul T.
XIP dlls Mobile Apps I develop a device that runs an application that uses multiple dlls. These dlls are big (around 4 MB and 6 dlls for at total of around 24 MB). This leaves us only a little space in we somtimes go out of memory. I read that it is possible to have XIP dlls that would load in slot 1 intead for slot 0. This would allow us to free memory. Does XIP dlls are slower at execution? Would it be possible for me to change theses dlls without having to recompile and reinstall the OS on the device? Of course we develop located into slot 0 when ROMIMAGE. Ok but would it be possible to have these dlls on a flash and have the ddls loaded after the driver? This would allow us
Default DLLs or SYSGENs found in WM5 Mobile Apps 3 Questions: 1: Does anyone know of the default DLLs (or SYSGENs) that *must* be in *all* Windows Mobile 5.0 devices, versus optional DLLs which *may* be present, versus DLLs that will *not* be present? 2: Relating to this question: If Windows Mobile 5 does not* come with a SYSGEN, and therefore related DLLs, is it possible for a Windows Mobile 5 software vendor to use PB 5 to generate the missing SYSGEN, and related DLLs, and then include some, if not all of the DLLs, for redistribution with the WM5 application? 3: If this is not generally acceptable, how can could.) WindowsCE Embedded Discussions Windows Mobile 5.0 (1) OpenNETCF (1) SYSGENs (1) LIBs (1) DLLs (1) Tacke (1) Redist (1) Whan (1) This would be covered under the WM NDA
XIP Dlls Mobile Apps Hi, Can some one please tell me more about XIP (eXecution In Place) Dlls. I heard that this mode determines how the dlls will be loaded into memory. Whether it is on demand basis or it will be not in used. Am I correct to state this? Sincerely Jimmy WindowsCE Platform Builder Discussions Dlls (1) AC5104510FD7 (1) XIP (1) Since you didn't say, I guess I'll assume CE5. XIP DLLs are executed in their default location, with no decompression or movement to RAM. That is your nk.bin image is written into linear flash and executed directly from flash, XIP DLLs will also be executed directly from flash. Non-XIP DLLs will be loaded from their image in flash, decompressed, and placed in RAM for execution So, no, you're not correct. XIP DLLs are never 'loaded'. They just sit where they are in the OS image and are