whql ndis driver

Hi,

I am looking to sign our NDIS vitual miniport driver signed under NDIS
universal test. One of the requirement is that the driver be "free of OS
specific kernel (ntoskrnl) calls". What function calls fall into this
category? For example, IoCancelIrp(), IoBuildPartialMdl()?, IoCsqXXX()?

thanks a lot,
Ning

Nazan
Mon Nov 21 18:06:18 CST 2005

NDISTest 1c_KernelCalls test tests your driver for these calls. If you pass
it, your driver is clean. It will also point out the calls your driver makes
that fall in to this category.

-Nazan
This posting is provided "AS IS" with no warranties, and confers no rights.

"ning" <ning@newsgroup.nospam> wrote in message
news:uIh4rQr7FHA.252@TK2MSFTNGP15.phx.gbl...
> Hi,
>
> I am looking to sign our NDIS vitual miniport driver signed under NDIS
> universal test. One of the requirement is that the driver be "free of OS
> specific kernel (ntoskrnl) calls". What function calls fall into this
> category? For example, IoCancelIrp(), IoBuildPartialMdl()?, IoCsqXXX()?
>
> thanks a lot,
> Ning
>

Maxim
Tue Nov 22 13:11:06 CST 2005

This means - you can ONLY call NdisXxx functions.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"ning" <ning@newsgroup.nospam> wrote in message
news:uIh4rQr7FHA.252@TK2MSFTNGP15.phx.gbl...
> Hi,
>
> I am looking to sign our NDIS vitual miniport driver signed under NDIS
> universal test. One of the requirement is that the driver be "free of OS
> specific kernel (ntoskrnl) calls". What function calls fall into this
> category? For example, IoCancelIrp(), IoBuildPartialMdl()?, IoCsqXXX()?
>
> thanks a lot,
> Ning
>
>

Calvin
Tue Nov 22 14:06:20 CST 2005

Well, the word "ONLY" is a little bit too strong here. As long as NDIStester
is happy with the driver. It should be fine.

--
Calvin Guan (Windows DDK MVP)
NetXtreme Longhorn Miniport Prime
Broadcom Corp. www.broadcom.com

"Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
news:%23KL8wh57FHA.3804@TK2MSFTNGP14.phx.gbl...
> This means - you can ONLY call NdisXxx functions.
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> maxim@storagecraft.com
> http://www.storagecraft.com
>
> "ning" <ning@newsgroup.nospam> wrote in message
> news:uIh4rQr7FHA.252@TK2MSFTNGP15.phx.gbl...
>> Hi,
>>
>> I am looking to sign our NDIS vitual miniport driver signed under NDIS
>> universal test. One of the requirement is that the driver be "free of OS
>> specific kernel (ntoskrnl) calls". What function calls fall into this
>> category? For example, IoCancelIrp(), IoBuildPartialMdl()?, IoCsqXXX()?
>>
>> thanks a lot,
>> Ning
>>
>>
>

ning
Wed Nov 23 09:20:03 CST 2005

Thanks for your responses. I run the kernel call test and it passed. Even
though I have a bunch of non-NDISXXX calls in my code. I looks like MS is
intentionally vague about what constitutes "kernel calls" within the scope
of whql.

Ning
"Calvin Guan" <hguan@nospam.broadcom.com> wrote in message
news:uZBW5A67FHA.2036@TK2MSFTNGP14.phx.gbl...
> Well, the word "ONLY" is a little bit too strong here. As long as
> NDIStester is happy with the driver. It should be fine.
>
> --
> Calvin Guan (Windows DDK MVP)
> NetXtreme Longhorn Miniport Prime
> Broadcom Corp. www.broadcom.com
>
> "Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
> news:%23KL8wh57FHA.3804@TK2MSFTNGP14.phx.gbl...
>> This means - you can ONLY call NdisXxx functions.
>>
>> --
>> Maxim Shatskih, Windows DDK MVP
>> StorageCraft Corporation
>> maxim@storagecraft.com
>> http://www.storagecraft.com
>>
>> "ning" <ning@newsgroup.nospam> wrote in message
>> news:uIh4rQr7FHA.252@TK2MSFTNGP15.phx.gbl...
>>> Hi,
>>>
>>> I am looking to sign our NDIS vitual miniport driver signed under NDIS
>>> universal test. One of the requirement is that the driver be "free of OS
>>> specific kernel (ntoskrnl) calls". What function calls fall into this
>>> category? For example, IoCancelIrp(), IoBuildPartialMdl()?, IoCsqXXX()?
>>>
>>> thanks a lot,
>>> Ning
>>>
>>>
>>
>
>

bburgin
Mon Nov 28 10:43:37 CST 2005

------=_NextPart_0001_2CC08552
Content-Type: text/plain
Content-Transfer-Encoding: 7bit



Also keep in mind that some NDIS "functions" are actually macros that
result in non-NDIS system calls being imported. The key is that it passed
the tests.

Bryan S. Burgin
bburgin@online.microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_2CC08552
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20
\par
\par Also keep in mind that some NDIS "functions" are actually macros that result in non-NDIS system calls being imported. The key is that it passed the tests.
\par
\par Bryan S. Burgin
\par bburgin@online.microsoft.com
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_2CC08552--

Maxim
Mon Nov 28 14:52:17 CST 2005

IIRC the callable implementation also exists in NDIS.SYS, and one can use
BINARY_COMPATIBLE macro to force the callable implementation.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

""Bryan S. Burgin [MSFT]"" <bburgin@online.microsoft.com> wrote in message
news:PxwckrD9FHA.832@TK2MSFTNGXA02.phx.gbl...
>
>
> Also keep in mind that some NDIS "functions" are actually macros that
> result in non-NDIS system calls being imported. The key is that it passed
> the tests.
>
> Bryan S. Burgin
> bburgin@online.microsoft.com
>
> This posting is provided "AS IS" with no warranties, and confers no rights.