In this example the mad16 kernel device driver depends on the ad1848 device driver.
在这个例子里面，mad16内核设备驱动程序依赖于ad1848驱动。
What you'll find is a variation in design and usage of the available kernel APIs, but each is useful for instruction or as a starting point for a new device driver.
在这里可以找到的是各种设计的变化以及对可用内核api的使用，但是所学到的每一点都会非常有用，都可以作为新设备驱动程序的起点。
DSF is especially helpful in executing device driver kernel code where the device may not be present.
当设备可能不存在时，DSF特别有助于执行设备驱动程序内核代码。
It could be in the kernel core per se, or in a device driver that is linked into the kernel either statically or dynamically.
它本身可以在内核中，也可以在静态或动态链接到内核的设备驱动例程中。
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函数中进行销毁。
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 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设备驱动程序。
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）中给出的信息记录下来。
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。
TAP is a virtual network kernel driver that implements an Ethernet device and as such, operates at the Ethernet frame level.
TAP是一个虚拟网络内核驱动，该驱动实现Ethernet设备，并在Ethernet框架级别操作。
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的符号链接。
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协议栈是使设备工作的主要内核层。
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内核中设备驱动程序的稳定性。
In practice, buffering may occur at various other levels, such as on the hard disk itself, the controller, or the kernel disk drive device driver, so ours may not make much of a difference.
实际上，缓冲可能发生在其它不同的级别，例如硬盘本身、控制器或内核磁盘驱动设备驱动程序，所以我们的工作可能对性能影响不大。
That way, when a process performs an operation on the device, the kernel knows what device driver should be referenced.
这样，进程对设备执行操作时，内核就会知道应该引用什么设备驱动程序。
All this kernel needs to have loaded into it is the device driver for the disk on which the other, loadable, modules are being kept.
这种内核所需要加载的东西就是磁盘的设备驱动程序，其他可加载的模块都可以保存在磁盘上。
This section highlights some of the important aspects of device driver porting from the 2.4 to 2.6 kernel.
本节重点介绍将驱动程序从2.4内核移植到2.6内核的一些重要方面。
When they are accessed, the kernel maps to the appropriate device driver by devfs device name, rather than by major number.
当它们被访问时，内核通过devfs设备名称映射到合适的设备驱动程序，而不是通过主设备号。
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 系统无关）。
The Training Program first classes will be Essential Linux Device Driver Development Skills; Creating Applications for Linux; and Kernel Debugging and Performance.
这一培训计划的首批课程将是精华：Linux设备驱动程序开发技能、创建Linux应用程序、以及内核调试与性能。
The kernel module implements a driver for a virtual block device (which is replicated between a local disk and a remote disk across the network).
内核模块实现一个用于虚拟块设备(跨网络在本地磁盘与远程磁盘之间复制)的驱动程序。
The first two courses, drawn from the selection of available on-site offerings, will be Essential Linux Device Driver Development Skills and Linux Kernel Debugging and Performance.
在网站上提供的头两个课程将是linux设备驱动程序开发技术基础和linux内核调试与性能。
The driver stores, in private data structures, all the information needed to drive the device and interact with other kernel components that require the device.
在驱动的私有数据结构中，驱动程序保存了所有的用于驱动设备的必要信息以及与内核交互时必须的组件信息。
The registration and initialization tasks are taken care of partially by the core kernel and partially by the device driver.
设备的注册和初始化就做这样的事，部份与内核相关，部份与设备驱动相关。
Update Package is unable to build a device driver for the running kernel because the required kernel source files are not installed.
更新软件包无法为当前运行的内核构建设备驱动程序，因为没有安装所需的内核源文件。
According to the isolation positions of device drivers, the device driver framework can be classified into three types: kernel mode driver, user mode driver and virtual machine based driver.
目前，对设备驱动可靠性的研究着重于设备驱动与操作系统内核的有效分离，设备驱动框架按照驱动被隔离所处位置大致可分为内核态、用户态和虚拟机三种。
According to the isolation positions of device drivers, the device driver framework can be classified into three types: kernel mode driver, user mode driver and virtual machine based driver.
目前，对设备驱动可靠性的研究着重于设备驱动与操作系统内核的有效分离，设备驱动框架按照驱动被隔离所处位置大致可分为内核态、用户态和虚拟机三种。
应用推荐