120楼#
发布于:2002-10-25 09:11
不关了,真累
|
|
|
121楼#
发布于:2002-10-25 09:19
;)天啊!怎么全是猪猪啊???真不懂。
|
|
|
122楼#
发布于:2002-10-25 09:20
呵呵,一起灌
|
|
|
123楼#
发布于:2002-10-25 09:40
曾一下 :D
|
|
124楼#
发布于:2002-10-25 09:45
An intermediate driver or miniport driver may require a separate, stand-alone device object. For example, an intermediate miniport driver might require a stand-alone device object to monitor the status of an underlying NIC when the NIC\'s miniport driver is not up and running. To obtain the NIC\'s status in such a case, a user-mode application or environmental subsystem sends an IRP to the device object. The IRP is processed by the intermediate driver. Without the stand-alone device object, the NIC\'s status is available only when the NIC\'s miniport driver is up and running.
|
|
|
125楼#
发布于:2002-10-25 09:46
An intermediate driver or miniport driver creates a device object by calling NdisMRegisterDevice from its DriverEntry function after DriverEntry has called NdisMInitializeWrapper. NdisMRegisterDevice creates a named device object and also a symbolic link between the device object name and a user-visible name for that device. If the call to NdisMRegisterDevice succeeds, the I/O Manager allocates storage in nonpaged pool for the device object itself and for all other data structures associated with the device object, including the driver\'s device extension. The device extension for an object created with NdisMRegisterDevice is reserved for use by NDIS and cannot be used by the driver.
|
|
|
126楼#
发布于:2002-10-25 09:48
A device object created with NdisMRegisterDevice functions in the same way as a device object and symbolic link that were created with IoCreateDevice and IoCreateSymbolicLink, respectively. IRPs sent to the device object are processed by the driver that created the device object―not by NDIS. The driver processes IRPs sent to the device object using dispatch routines that it registered when it supplied the MajorFunctions pointer to NdisMRegisterDevice. For more information on device objects, IRPs, and dispatch routines, see Device Objects and Device Stacks, Handling IRPs, and Writing Dispatch Routines.
|
|
|
127楼#
发布于:2002-10-25 09:51
NDIS drivers should never call IoCreateDevice or IoCreateSymbolicLink. Instead, if an NDIS driver must create a device object, it should call NdisMRegisterDevice
重要! |
|
|
128楼#
发布于:2002-10-25 09:54
The device object that is created with NdisMRegisterDevice is not a physical device object and therefore does not receive Plug and Play or Power Management IRPs. Callers of NdisMRegisterDevice must therefore omit entry points for Plug and Play or Power Management handlers in the array that is pointed to by MajorFunctions.
|
|
|
129楼#
发布于:2002-10-25 09:54
先手几分再说
|
|
|
130楼#
发布于:2002-10-25 09:54
If a driver\'s call to NdisMRegisterDevice fails, the driver can continue to load or not, depending on how critical the stand-alone device object is for the driver\'s operation.
|
|
|
131楼#
发布于:2002-10-25 09:55
Callers of NdisMRegisterDevice run at IRQL PASSIVE_LEVEL
|
|
|
132楼#
发布于:2002-10-25 09:55
给我
|
|
|
133楼#
发布于:2002-10-25 09:57
收几分再说
|
|
|
134楼#
发布于:2002-10-25 10:03
放这么多还叫小放一把。
|
|
135楼#
发布于:2002-10-25 10:05
DLM真是money多多呀。
|
|
136楼#
发布于:2002-10-25 10:05
再收几分 :D
|
|
|
137楼#
发布于:2002-10-25 10:32
我也要
1哈哈~~~~~ ;) :P ;) :D :) :P |
|
|
138楼#
发布于:2002-10-25 11:33
除了通用的平台服务和扩展外,WDM还实现了一个模块化的、分层次类型的微型驱动程序结构(见图1)。类型驱动程序实现了支持通用总线、协议或设备类所需的功能性接口。类型驱动程序的一般特性是为逻辑设备的命令设置、协议和代码重用所需的总线接口实现标准化提供必要的条件。WDM对标准类接口的支持减少了
|
|
139楼#
发布于:2002-10-25 11:33
Windows 95和Windows NT所需的设备驱动程序的数量和复杂性。Windows 2000也引入了WDM驱动程序构架。虽然WDM目前实际应用还不多,但是相信在不久的将来,在Windows平台上,WDM将成为21世纪主流的驱动模式。
|
|