有时也使用第三方设备驱动程序。
考虑这样一个假想的设备驱动程序。
你也许认为，我准备谈论设备驱动程序的质量。
You may think I am now going to talk about the quality of the device drivers.
还需要对设备驱动程序应用一个补丁(附加例程)。
You will also be applying a patch (extra routines) to your device driver.
为什么会有人想要在开发设备驱动程序时模拟硬件呢？
Why would anybody want to simulate hardware when developing a device driver?
网络栈底部是负责管理物理网络设备的设备驱动程序。
At the bottom of the network stack are the device drivers that manage the physical network devices.
一般而言，设备句柄由具体设备驱动程序的名称决定。
Generally speaking, the device handle is determined by the name of a particular device driver.
并包含U SB设备驱动程序可以使用的函数和数据结构。
It contains functions and data structures that USB device drivers can use.
此外，如果您的设备驱动程序支持，则可以使用友好的名称。
Also, you can use friendly name if your device driver supports it.
一般来说，设备驱动程序不需要实现aio_fsync 。
As a general rule, device drivers will not need to implement aio_fsync .
对特定设备的访问由与它相关联的传统物理设备驱动程序处理。
The access to a specific device is handled by traditional physical device driver associated with it.
用于访问硬件的所有设备驱动程序也都被装载到Dom 0中。
All the device drivers for accessing hardware are also loaded in Dom0.
例如，对底层设备驱动程序的读写请求会通过缓冲区缓存来传递。
For example, read and write requests to the underlying device drivers migrate through the buffer cache.
缓冲区缓存之下是设备驱动程序，它实现了特定物理设备的接口。
Below the buffer cache are the device drivers, which implement the interface for the particular physical device.
这些内核线程应该在设备驱动程序的close函数中进行销毁。
These kernel threads should be destroyed in the close of the device driver.
这个模块唯一的特性就是它利用设备驱动程序提供的透明负载均衡。
One unique feature of this module is that it takes advantage of the transparent load balancing provided by the device driver.
然后内核开始启动，设备驱动程序开始向系统的剩余部分注册设备。
Then, the kernel starts to boot and device drivers begin to register devices with the rest of the system.
这种策略让我们可以按照每个中断来跟踪设备驱动程序的完整代码。
This strategy lets you examine the device driver's complete code flow on a per-interrupt basis.
举例来说，假设foo设备驱动程序希望使用devfs注册设备。
For example, let's say that the foo device driver wants to register a device with devfs.
现在我们可以在VisualStudio中开发设备驱动程序。
当设备可能不存在时，DSF特别有助于执行设备驱动程序内核代码。
DSF is especially helpful in executing device driver kernel code where the device may not be present.
而称为设备驱动程序的内核中软件的特殊部分就充当这些设备的封装器。
Instead, special pieces of software inside the kernel called device drivers act as wrappers to these devices.
DeviceName应当与相应设备驱动程序定义的设备名称相同。
DeviceName should be the same as the device name defined in the corresponding device driver program.
最底层是屏幕和输入设备驱动程序(关于键盘或鼠标)来与实际硬件交互。
At the lowest level are the screen and input device drivers (as for the keyboard or mouse) to interact with the actual hardware.
这样，进程对设备执行操作时，内核就会知道应该引用什么设备驱动程序。
That way, when a process performs an operation on the device, the kernel knows what device driver should be referenced.
当您调换适配器时，现在的设备驱动程序会支持此适配器，因为它是同类型的。
When you exchange the adapter, the existing device driver supports the adapter because it is of the same type.
本文通过模拟各种中断，尽可能地帮助设备驱动程序开发人员测试中断服务例程。
This article helps device driver developers test the interrupt service routine as much as possible by simulating the various interrupts.
根据设备驱动程序的不同，如果设备具有缓冲区，可能需要使用一个缓冲区的拷贝。
Depending on your device driver, you may need to have a copy of the buffers, if the device has any.
本节着重讨论通常几乎在每个嵌入式环境中都会使用的一些重要设备的设备驱动程序。
This section focuses on device drivers for some important devices that are normally used in almost every embedded environment.
对物理存储器的访问：诸如设备驱动程序之类的RT应用程序总是需要追溯根源。
Access to physical memory: RT applications such as device drivers often need to get down to the metal.
应用推荐