Ndis6.0 MiniportInitialization information required?

NTDEV
1

Dear Developers,

Greetings!!!

As, I am developing miniport driver for ndis6.0 framework on WinCE 7 platform. I have completed the DriverEntry part and successfully register my miniport driver with NDIS framework.

I am working in MPInitializationEx part and there I have done the following things in the flow mentioned : -

  1. Configured NDIS_CONFIGURATION_OBJECT
  2. Able to access the parameters of registry using NdisOpenConfigurationEx
  3. Able to register miniport attributes in NDIS_MINIPORT_ADAPTER_ATTRIBUTES
  4. Able to set some general miniport attributes in NDIS_MINIPORT_ADAPTER_GENERAL_ATTRIBUTES

As, I am taking the reference of Pro_Windows_Embedded_Compact_7.pdf reference.
There, I can see some local functions for MPInitializationEx as: -
MpAllocAdapterBlock
NICReadRegParameters
MpFindAdapter
NICInitSend
NICInitRecv
NICSelfTest
NICInitializeAdapter

What are all these functions…
As, the information given in
https://msdn.microsoft.com/en-in/library/gg157001(v=winembedded.70).aspx
for MPInitializeEx is not matching according to the above local function…

One thing I know that in this MPInitializationEx, we have to init the Adapter and load the firmware.

But I have no information to proceed forward. Where can I get the exact info so that I can close my MPInitializeEx

2

xxxxx@gmail.com wrote:

As, I am developing miniport driver for ndis6.0 framework on WinCE 7 platform. I have completed the DriverEntry part and successfully register my miniport driver with NDIS framework.

I am working in MPInitializationEx part and there I have done the following things in the flow mentioned : -

What is your overall goal here? Do you actually have a new type of
network interface device that you need to support? Do you have the
complete specs for that device?

Almost no one writes an NDIS driver by starting with a blank sheet of
paper and coding it from scratch. Because most network devices tend to
be very similar to one another, most people start from one of the
samples and modify it. The samples include comments that explain why
certain decisions were made.

As, I am taking the reference of Pro_Windows_Embedded_Compact_7.pdf reference.
There, I can see some local functions for MPInitializationEx as: -
MpAllocAdapterBlock
NICReadRegParameters
MpFindAdapter
NICInitSend
NICInitRecv
NICSelfTest
NICInitializeAdapter

What are all these functions…

We don’t know. You’re the one with the book. If their sample is
calling those functions, then they should show you those functions.
Those are just the choices made by the
author of that driver. You might need an entirely different set of
helper functions in your initialization.

As, the information given in
https://msdn.microsoft.com/en-in/library/gg157001(v=winembedded.70).aspx
for MPInitializeEx is not matching according to the above local function…

That’s not true. The documentation tells you in general terms what the
callback is expected to do. It doesn’t determine the exact
implementation. That’s up to the driver writer.

One thing I know that in this MPInitializationEx, we have to init the Adapter and load the firmware.

Right, assuming the device has firmware. That’s likely what those
helper functions were doing, based on names like “NICInitializeAdapter”.

But I have no information to proceed forward. Where can I get the exact info so that I can close my MPInitializeEx

This is YOUR job. Based on your knowledge of the board you plan to
support, YOU need to figure out what things have to be initialized to
get your board ready to operate. We can’t tell you that.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.