Checksum of device drivers and methods.
设备驱动器和方法的校验和。
Host Based with Special Device drivers.
基于托管并提供特殊设备驱动。
Sometimes third-party device drivers are even used.
有时也使用第三方设备驱动程序。
It was. Few developers write device drivers any more.
正因如此，几乎没有开发者再写那些设备驱动。
The SCSI subsystem is one of these block device drivers.
scsi子系统是这种块设备驱动器之一。
Only the kernel and some device drivers are written in c.
只有内核和一些设备驱动是用c编写的。
Device drivers can now be developed within Visual Studio.
现在我们可以在VisualStudio中开发设备驱动程序。
All the device drivers for accessing hardware are also loaded in Dom0.
用于访问硬件的所有设备驱动程序也都被装载到Dom 0中。
The majority of code in most modern kernels is found in device drivers.
在现代内核中，大部分代码出现在设备驱动中。
This means that block device drivers need to be redesigned from 2.4.
这意味着原来用于2.4的块设备需要进行重新设计。
As a general rule, device drivers will not need to implement aio_fsync .
一般来说，设备驱动程序不需要实现aio_fsync 。
However, there are some important changes that affect device drivers.
不过，还是有一些重要的变化会影响到驱动程序开发者。
The device drivers known to the system and which device (s) they control.
系统清楚设备的驱动程序，并清楚哪些设备受其控制。
It contains functions and data structures that USB device drivers can use.
并包含U SB设备驱动程序可以使用的函数和数据结构。
You may think I am now going to talk about the quality of the device drivers.
你也许认为，我准备谈论设备驱动程序的质量。
IrDa chips incompatible with the serial driver have their own device drivers.
与串行驱动器不兼容的IrDa芯片有自己的设备驱动程序。
Upgraded the BIOS and device drivers for the IBM ServRAID adapter to 2.82 or higher.
为IBMServRAID适配器将BIOS和设备驱动器更新到2.82或更高版本。
LKMs are also a popular mechanism for device drivers and filesystems in the Linux kernel.
LKM也是Linux内核中为设备驱动程序和文件系统使用的一种流行机制。
Linux device drivers work through special kernel code that directly accesses the hardware.
Linux设备驱动程序，是通过专门与硬件打交道的内核代码工作的。
This approach also requires support of the right device drivers, ports, and vendor devices.
这一方法也需要支持正确的设备驱动、端口和供应商设备。
In short, with Hyper-V, you never want to run virtual machines with emulated device drivers.
总之，在Hyper - V中，你永远不想用模拟设备驱动运行虚拟机！
The code I touched during that work relates mostly to device drivers to support the framework.
我在工作中所接触的代码只与支持框架的设备驱动有关。
This queue is managed bv Linux's "netdevice" layer that sits in-between IP and device drivers.
该队列由Linux的“netdevice”层来管理，它位于IP和设备驱动之间。
At the bottom of the network stack are the device drivers that manage the physical network devices.
网络栈底部是负责管理物理网络设备的设备驱动程序。
Access to physical memory: RT applications such as device drivers often need to get down to the metal.
对物理存储器的访问：诸如设备驱动程序之类的RT应用程序总是需要追溯根源。
For example, read and write requests to the underlying device drivers migrate through the buffer cache.
例如，对底层设备驱动程序的读写请求会通过缓冲区缓存来传递。
Next is the block device drivers layer, which contains the various block drivers for underlying devices.
接下来是块设备驱动器层，它包括针对底层设备的各种块驱动器。
Then, the kernel starts to boot and device drivers begin to register devices with the rest of the system.
然后内核开始启动，设备驱动程序开始向系统的剩余部分注册设备。
Limited changes to support new hardware, such as device drivers' kernels changes to reflect a new processor.
为支持新硬件而实施的有限修改，比如修改设备驱动程序的内核以反映一种新的处理器。
Instead, special pieces of software inside the kernel called device drivers act as wrappers to these devices.
而称为设备驱动程序的内核中软件的特殊部分就充当这些设备的封装器。
应用推荐