driver is a wrapper designed to allow binary
network drivers to be used with
driver is provided in source code form and must be combined with
driver supplied with your network adapter.
driver uses the
kernel subsystem to relocate and link the
that it can be used in conjunction with native code.
subsystem provides an interface between the NDIS API and the
driver is essentially
fooled into thinking it is running on
Note that this
driver is only useful on x86 machines.
To build a functional driver, the user must have a copy of the
driver distribution media for his or her card.
From this distribution,
the user must extract two files: the
file containing the driver
binary code, and its companion
file, which contains the
definitions for driver-specific registry keys and other installation
data such as device identifiers.
These two files can be converted
into a kernel module file using the
This file contains a binary image of the driver plus
registry key data.
driver loads, it will create
nodes for each registry key extracted from the
driver is designed to support mainly Ethernet and wireless
network devices with PCI, PCMCIA and USB bus attachments.
devices are also supported as a subset of PCI.)
support many different media types and speeds.
however, is that there is no consistent way to learn if an
Ethernet device is operating in full or half duplex mode.
The NDIS API allows for a generic means for determining link
state and speed, but not the duplex setting.
There may be
driver-specific registry keys to control the media setting
which can be configured via the