TAP is a virtual network kernel driver that implements an Ethernet device and as such, operates at the Ethernet frame level.
TAP是一个虚拟网络内核驱动，该驱动实现Ethernet设备，并在Ethernet框架级别操作。
The library does not require you to write any line of kernel driver code, which makes it really easy to use and implement.
该库不需要你写任何行的内核驱动程序代码，这使得它非常容易使用和实现。
And that means that the BIOS isn't just taking up half the time from power-on to the last kernel driver loaded; it's probably taking up a lot more.
这意味着BIOS不仅要花从加电到最后一个内核模块加载时间的一半在这上面；有时还可能会花费更多时间。
The mapping from special file to kernel driver is made possible by the major number, not the actual device name, which is irrelevant to a non-devfs system.
让特殊文件到内核驱动程序的映射成为可能的是主设备号，而不是真实的设备名称（它和非 devfs 系统无关）。
Currently these packets must travel from the host kernel driver, passing the TAP32 driver, colinux-net daemon, colinux daemon, and then ending up in colinux kernel driver.
当前，这些数据包必须从宿主驱动程序开始，经过TAP32驱动程序、colinux - net后台进程、colinux后台进程，最后到达colinux内核驱动程序。
By bypassing these steps and replacing them with direct guest kernel driver/colinux driver link, we can reduce the communication latency and thus enhance the cluster performance.
绕开这些步骤并将其替换 为直接的内核驱动程序/colinux 驱动程序连接，这样就可以减少通信延迟，从而提高集群的性能。
DSF is especially helpful in executing device driver kernel code where the device may not be present.
当设备可能不存在时，DSF特别有助于执行设备驱动程序内核代码。
But if, say, a printer driver suddenly erases the kernel code needed to access the disk drive, the operating system will have part of its brain cut out.
但是，比如一个打印机驱动程序突然把接磁盘驱动所需的核心代码删除掉，操作系统就会出现部分停顿。
It could be in the kernel core per se, or in a device driver that is linked into the kernel either statically or dynamically.
它本身可以在内核中，也可以在静态或动态链接到内核的设备驱动例程中。
I've received some messages, that it is not possible to compile the driver for kernel 2.6.
我已经接到一些信息，说在2.6版本的内核无法编译驱动。
If a driver is compiled directly into the kernel, its code and static data occupy space even if they're not used.
如果一个驱动程序被直接编译到了内核中，那么即使这个驱动程序没有运行，它的代码和静态数据也会占据一部分空间。
For audio, the default Linux kernel sound driver supports a wide variety of devices, but it pays to research your device, particularly if it is built-in on the motherboard.
对于音频而言，默认的Linux内核声音驱动程序支持一组广泛的设备，但研究您的设备是有回报的，特别是当它内置在主板中时。
These kernel threads should be destroyed in the close of the device driver.
这些内核线程应该在设备驱动程序的close函数中进行销毁。
This kernel thread should be destroyed in the close of the device driver in this pseudo code.
在下面的伪代码中，这个内核线程应该在设备驱动程序的close函数中进行销毁。
In response, devfs_register adds the foo0 device node to the root of the devfs namespace, and records that this new foo0 node should map to the foo device driver in the kernel.
相应的，devfs_register在devfs名称空间的根目录添加foo0设备节点，并记录这个新的foo0节点应该映射到内核中的foo设备驱动程序。
To visit the device, the Linux kernel maps the device operation call to the device driver via the file system.
为了访问设备，Linux内核将设备操作调用通过文件系统映射到设备驱动程序。
The above rule says: match a device which was named by the kernel as hdb AND where the driver is ide-disk. Name the device node with the default name and create a symbolic link to it named sparedisk.
上面规则意思是：匹配一个内核命名为hdb以及驱动为ide-disk的设备，命名设备节点为缺省名字,同时创建一个指向它的名为sparedisk的符号链接。
Within a driver, the mmap function is implemented through the remap_pfn_range kernel function, which provides a linear mapping of device memory into a user's address space.
在一个驱动程序中，mmap函数通过remap _ pfn_range内核函数实现，它提供设备内存到用户地址空间的线性映射。
In this example the mad16 kernel device driver depends on the ad1848 device driver.
在这个例子里面，mad16内核设备驱动程序依赖于ad1848驱动。
The 2.6 kernel has brought along with it a pretty significant list of changes for driver developers.
6内核给驱动程序开发人员带来了一系列非常有意义的变化。
The Linux kernel occupies a single address space, which means that a failure of the kernel or any driver results in the entire operating system crashing.
Linux内核占据了一个单一的地址空间，这意味着内核或任何驱动程序的故障都会导致整个操作系统的崩溃。
The device entry in Listing 1 states that the orinoco_cs driver consists of three kernel modules: Orinoco, orinoco_cs, and hermes.
清单1中的设备条目规定orinoco_cs驱动程序由三个内核模块组成：orinoco、orinoco_cs和hermes。
The goal of the Linux test Project is to help device driver developers standardize device unit tests and increase device driver stability in the Linux kernel.
LinuxTestProject的目标是帮助设备驱动程序开发人员标准化设备单元测试，提高Linux内核中设备驱动程序的稳定性。
The kernel trace hooks call functions in the device driver code, which log the information provided by the kernel trace hooks in pinned buffers.
内核追踪挂钩调用设备驱动程序代码中的函数，那些函数将内核追踪挂钩在固定缓冲区（pinned buffer）中给出的信息记录下来。
Therefore, the Linux USB layer, the BlueZ USB transport driver, and the BlueZ protocol stack are the main kernel layers that get the device working.
因此，LinuxUS b层、BlueZ US b传输器驱动程序以及BlueZ协议栈是使设备工作的主要内核层。
Therefore, the Linux USB layer, the BlueZ USB transport driver, and the BlueZ protocol stack are the main kernel layers that get the device working.
因此，LinuxUS b层、BlueZ US b传输器驱动程序以及BlueZ协议栈是使设备工作的主要内核层。
应用推荐