Bill Paul ca989c99d0 Attempt to handle the status field in the ndis_packet oob area correctly. ... For received packets, an status of NDIS_STATUS_RESOURCES means we need to copy the packet data and return the ndis_packet to the driver immediatel. NDIS_STATUS_SUCCESS means we get to hold onto the packet, but we have to set the status to NDIS_STATUS_PENDING so the driver knows we're going to hang onto it for a while. For transmit packets, NDIS_STATUS_PENDING means the driver will asynchronously return the packet to us via the ndis_txeof() routine, and NDIS_STATUS_SUCCESS means the driver sent the frame, and NDIS (i.e. the OS) retains ownership of the packet and can free it right away.		2003-12-26 07:01:05 +00:00
..
cfg_var.h	Deal with the duplicate sysctl leaf problem. A .inf file may contain	2003-12-18 03:51:21 +00:00
hal_var.h
kern_ndis.c	Attempt to handle the status field in the ndis_packet oob area correctly.	2003-12-26 07:01:05 +00:00
ndis_var.h	Back out the last batch of changes until I have a chance to properly	2003-12-26 03:31:34 +00:00
ntoskrnl_var.h	Re-do the handling of ndis_buffers. The NDIS_BUFFER structure is	2003-12-23 04:08:22 +00:00
pe_var.h
resource_var.h
subr_hal.c
subr_ndis.c	Back out the last batch of changes until I have a chance to properly	2003-12-26 03:31:34 +00:00
subr_ntoskrnl.c	- Add stubs for Ndis*File() functions	2003-12-25 00:40:02 +00:00
subr_pe.c	Back out the last batch of changes until I have a chance to properly	2003-12-26 03:31:34 +00:00