Overview of RNDIS
来源:互联网 发布:nginx proxy_pass 编辑:程序博客网 时间:2024/06/15 07:06
Remote NDIS (RNDIS) eliminates the need for hardware vendors to write an NDIS miniport device driver for a network device attached to the USB bus. Remote NDIS accomplishes this by defining a bus-independent message set and a description of how this message set operates over the USB bus. Because this Remote NDIS interface is standardized, one set of host drivers can support any number of networking devices attached to the USB bus. This significantly reduces the development burden on device manufacturers, improves the overall stability of the system because no new drivers are required, and improves the end-user experience because there are no drivers to install to support a new USB bus-connected network device. Currently Microsoft Windows provides support for Remote NDIS over USB.
The following figure shows the replacement of the device manufacturer's NDIS miniport with the combination of a Remote NDIS miniport driver and a USB transport driver. The device manufacturer can therefore concentrate on device implementation and not have to develop a Windows NDIS device driver.
Microsoft provides an NDIS miniport driver, Rndismp.sys, which implements the Remote NDIS message set and communicates with generic bus transport drivers, which in turn communicate with the appropriate bus driver. This NDIS miniport driver is implemented and maintained by Microsoft and is distributed as part of Windows.
The following Remote NDIS message set mirrors the semantics of the NDIS miniport driver interface:
Initializing, resetting, and halting device operation
Transmitting and receiving networking data packets
Setting and querying device operational parameters
Indicating media link status and monitoring device status
Microsoft also provides a USB bus transport driver that implements a mechanism for carrying the Remote NDIS messages across the USB bus. This driver transports standardized Remote NDIS messages between the Remote NDIS miniport driver and the bus-specific driver, such as USB. The bus-specific drivers are also required to map any bus-specific requirements, such as power management, into standardized Remote NDIS messages. The transport driver for USB 1.1 and 2.0 is implemented and maintained by Microsoft and distributed as part of Windows.
This structure allows a single device driver to be used for any Remote NDIS device for which there is a bus-specific transport layer. In addition, only one bus transport layer is required for all network devices on a specific bus.
This section includes the following additional topics:
Benefits of Remote NDIS
Remote NDIS Concepts and Definitions
Remote NDIS File Naming Conventions
Remote NDIS Messaging
Remote NDIS Device Control
Remote NDIS INF Template
Types of Remote NDIS Devices
...
- Overview of RNDIS
- rndis
- RNDIS
- Overview of ASP.NET
- [SilkTest]Overview of tags
- Overview of the Book
- Overview of Domain Models
- Overview of Models
- Overview of GSM protocol
- Overview of H323
- Overview of ACE
- Overview of webapp framework
- OVERVIEW OF EJB
- Overview of COCOMO
- An Overview of WebCore
- Overview of Soak testing
- Overview of malware inspection
- An overview of Android
- iframe父子页面使用
- JS获取单选按钮的值
- eclipse tomcat 启动45秒的问题
- eclipse中JS文件乱码
- list转json
- Overview of RNDIS
- jquery选择器
- 程序员的职业规划
- jquery dom 节点操作
- jquery 属性操作
- Texture Packer 优化Spritesheet 的使用
- 参加广州传智播客3G Android培训,不再为高薪工作忧愁
- jquery 样式 css
- jquery 函数