RE: sync/async NdisTransferData()

Hi Steve,
I have tried NDISTest tool.
Because I have poor equipment I run test on one machine,
support interface with test interface are connected with cross-over cable.
I choose CLIENT and 1 manual test named - "TransferData".
I am not sure if this way is OK for testing async NdisTransferData(), but
after test finished, the result was OK
for my IM driver without implemented ProtocolTransferDataComplete()
:-(

P.

"Steve" wrote:

I think running HCT (used for getting driver signed) will
generate all types of receive and allow your driver to be
tested. Alternative is to write your own IM or NIC
driver to simulate this.

It is important that your driver is capable of processing
all types - even if your user has a NIC that you specify,
they might have other IM drivers installed (i.e. vpn -
deterministic, etc.) and they might process receives
using old style!

Providing this support is not hard - email me if you need
help - remove _ZXXZ_ for valid email address.

Steve.


-----Original Message-----
Hi,
It would help me to hear one thing from programmer who
has experiences
with behaviour of many NIC types in NDIS environment.

The problem is relating to NIC-s that uses old style of
received packet
indicating.
In DDK doc is written that if NdisTransferData() returns
NDIS_STATUS_PENDING,
miniport driver after copying data calls
ProtocolTransferDataComplete().

I have tried only small amount of NIC types
and by my small expierences NdisTransferData() always
was executed
synchronously.
My question is:
When NIC driver cannot copy all data in NdisTransferData
() ?
Is it depending on NIC type ? Or it is depending on lack
of system resources
? or something other ?
Or only old scrap taiwan NIC-s cannot catch to copy all
data synchronously ?
(Consider only on W2K/XP/2003 and up)

The answer can help with my design/implementation.

Thanks !
Peter
.


.

Relevant Pages

  • Re: sync/async NdisTransferData()
    ... Is that only case when NIC driver can process NdisTransferData() ... must NIC to support DMA to process NdisTransferData() ... The Microsoft NDIS Tester, which is part of the HCT (Hardware ...
    (microsoft.public.development.device.drivers)
  • RE: sync/async NdisTransferData()
    ... support interface with test interface are connected with cross-over cable. ... for my IM driver without implemented ProtocolTransferDataComplete ... >>with behaviour of many NIC types in NDIS environment. ... >>In DDK doc is written that if NdisTransferData() returns ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS IM: ProtocolReceive() again
    ... WHEN my driver gets called at ProtocolReceive, ... NdisGetReceivedPacket(), ... i'm also NOT interested in NdisTransferData() because it is irrelevant ... to call NdisTransferDatawith this particular miniport i'm testing ...
    (microsoft.public.development.device.drivers)
  • sync/async NdisTransferData()
    ... I think running HCT (used for getting driver signed) will ... >with behaviour of many NIC types in NDIS environment. ... >In DDK doc is written that if NdisTransferData() returns ... >Is it depending on NIC type? ...
    (microsoft.public.development.device.drivers)
  • [PATCH 2/5] wistron: do not crash if BIOS does not support interface
    ... wistron - do not crash if BIOS does not support interface ... The driver ... currently oopses on insmod if BIOS does not support the interface, ...
    (Linux-Kernel)