mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-23 21:20:42 +08:00
[Translated] 22 The Linux Kernel--Configuring the Kernel Part 18
This commit is contained in:
geekpi
parent
d553e0d6c5
commit
8d6c038a49
@ -1,116 +0,0 @@
|
||||
Translating----------geekpi
|
||||
|
||||
|
||||
|
||||
22 The Linux Kernel: Configuring the Kernel Part 18
|
||||
================================================================================
|
||||
|
||||
|
||||
Aloha! Ready for the next article? In this article, we will discuss the auxiliary-screen. The auxiliary displays are small LCD screens; most are equal to or less than 128x64. Then, we will discuss Userspace IO drivers, some virtual drivers, Hyper-V, staging drivers, IOMMU, and other kernel features.
|
||||
|
||||
The first driver to configure for the auxiliary display is the "KS0108 LCD Controller" driver. The KS0108 LCD Controller is a graphics controller made by Samsung.
|
||||
|
||||
Next, the parallel port address for the LCD can be set (Parallel port where the LCD is connected). The first port address is 0x378, the next is 0x278 and the third is 0x3BC. These are not the only choices of addresses. The majority of people will not need to change this. The shell command "cat /proc/ioports" will list the available parallel ports and the addresses.
|
||||
|
||||
The kernel developer can set the writing delay of the KS0108 LCD Controller to the parallel port (Delay between each control writing (microseconds)). The default value is almost always correct, so this typically does not need to be changed.
|
||||
|
||||
The "CFAG12864B LCD" screen is a 128x64, two-color LCD screen. This screen relies on the KS0108 LCD Controller.
|
||||
|
||||
The refresh rate of these LCD screens can be changed (Refresh rate (hertz)). Generally, a higher refresh rate causes more CPU activity. This means slower systems will need a smaller refresh rate.
|
||||
|
||||
After the auxiliary displays are configured, the "Userspace I/O drivers" are then set. The userspace system allows the user's applications and processes to access kernel interrupts and memory addresses. With this enabled, some drivers will be placed in the userspace.
|
||||
|
||||
The "generic Hilscher CIF Card driver" is a userspace driver for Profibus cards and Hilscher CIF Cards.
|
||||
|
||||
The "Userspace I/O platform driver" creates a general system for drivers to be in the userspace.
|
||||
|
||||
The next driver is the same as above, but adds IRQ handling (Userspace I/O platform driver with generic IRQ handling).
|
||||
|
||||
The following driver is again like the one before, but with dynamic memory abilities added (Userspace platform driver with generic irq and dynamic memory).
|
||||
|
||||
Next, some vendor/device specific drivers are available.
|
||||
|
||||
Then, there is a generic PCI/PCIe card driver (Generic driver for PCI 2.3 and PCI Express cards).
|
||||
|
||||
The following driver is for "VFIO support for PCI devices". VFIO stands for Virtual Function Input/Output. VFIO allows devices to directly access userspace in a secure fashion.
|
||||
|
||||
The "VFIO PCI support for VGA devices" allows VGA to be supported by PCI through VFIO.
|
||||
|
||||
Next, are virtio drivers. Virtio is a IO virtualization platform. This virtual software is for operating system virtualization. This is required for running an operating system in a virtual machine on the Linux system.
|
||||
|
||||
The first virtio driver we can configure is the "PCI driver for virtio devices". This allows virtual access to PCI.
|
||||
|
||||
The "Virtio balloon driver" allows the memory owned by a virtual system to be expanded or decreased as needed. Generally, no one wants a virtual system to reserve memory it may never use when the host operating system needs the memory.
|
||||
|
||||
The following driver supports memory mapped virtio devices (Platform bus driver for memory mapped virtio devices).
|
||||
|
||||
If the Linux kernel being configured is intended to run on a Microsoft Hyper-V system, then enable this driver (Microsoft Hyper-V client drivers). This would allow Linux to be the guest/client system on Hyper-V.
|
||||
|
||||
|
||||
|
||||
Next, we have the staging drivers. These are drivers that are under development, may change soon, or are not up to the standard quality for the Linux kernel. The only group of drivers in this category (in this kernel version 3.9.4) are the Android drivers. Yes, Android uses the Linux kernel which would make Android a Linux system. However, this is still debated. If the kernel is intended for Android, then it may be wise to enable all of the drivers.
|
||||
|
||||
The "Android Binder IPC Driver" provides support for Binder which is a system that allows processes to communicate with each other on Android systems.
|
||||
|
||||
The ashmem driver can be enabled next (Enable the Anonymous Shared Memory Subsystem). Ashmem stands for "Anonymous SHared MEMory" or "Android SHared MEMory". This supports a file-based memory system for userspace.
|
||||
|
||||
The "Android log driver" offers the complete Android logging system.
|
||||
|
||||
The "Timed output class driver" and "Android timed gpio driver" allow the Android system to manipulate GPIO pins and undo the manipulations after the timeout.
|
||||
|
||||
The "Android Low Memory Killer" closes processes when more memory is needed. This feature kills the tasks that are not used or inactive.
|
||||
|
||||
The "Android alarm driver" makes the kernel wakeup at set intervals.
|
||||
|
||||
After the staging drivers are configured, the next set of drivers are for the X86 platform. These drivers are vendor/device specific for X86 (32-bit) hardware.
|
||||
|
||||
The next driver is for "Mailbox Hardware Support". This framework controls mailbox queues and interrupt signals for hardware mailbox systems.
|
||||
|
||||
"IOMMU Hardware Support" links the memory to devices that are able to use DMA. IOMMU enhances DMA. The IOMMU maps addresses and blocks faulty devices from accessing the memory. IOMMU also allows hardware to access more memory than it could without IOMMU.
|
||||
|
||||
The "AMD IOMMU support" driver offers better IOMMU support for AMD devices.
|
||||
|
||||
Debugging abilities exist for the AMD IOMMU support (Export AMD IOMMU statistics to debugfs).
|
||||
|
||||
A newer version of the IOMMU driver exists for AMD hardware (AMD IOMMU Version 2 driver).
|
||||
|
||||
The Linux kernel also provides an IOMMU driver specifically for Intel devices (Support for Intel IOMMU using DMA Remapping Devices).
|
||||
|
||||
Some devices may be able to accept a variety of voltages and clock frequencies. This driver allows the operating system to control the device's voltage output and clock rate (Generic Dynamic Voltage and Frequency Scaling (DVFS) support). With this driver enabled, other kernel features can be enabled for power/performance management as seen below.
|
||||
|
||||
"Simple Ondemand" is like above, but specifically changes the clock rate based on the device's activity. Generally, more activity means the device needs a faster clock speed to accommodate for the larger resource demand.
|
||||
|
||||
|
||||
"Performance" allows the system to set the clock speed to the maximum supported amount for best performance. This increases power consumption.
|
||||
|
||||
"Powersave" sets the clock rate to the lowest value to save power.
|
||||
|
||||
"Userspace" allows the userspace to set the clock speed.
|
||||
|
||||
"External Connector Class (extcon) support" provides the userspace with a way to watch external connectors like USB and AC ports. This allows applications to know if a cable was plugged into a port. Users will almost always want this enabled. If anyone has purposely disabled this for a legitimate reason, please share with us why that would be needed.
|
||||
|
||||
The "GPIO extcon support" driver is just like the above driver, but is made specifically for GPIO pins.
|
||||
|
||||
Next, there is a list of various vendor/device specific controllers for memory (Memory Controller drivers). Memory chip controllers may be separate devices or built inside the memory chips. These controllers manage the incoming and outgoing data flow.
|
||||
|
||||
The "Industrial I/O support" driver provides a standard interface for sensors despite the bus type they are on (that is, PCIe, spi, GPIO, etc.). IIO is a common abbreviation for Industrial Input/Output.
|
||||
|
||||
The Linux kernel offers support for a large variety of accelerometers, amplifiers, analog to digital converters, inertial measurement units, light sensors, magnetometer sensors, and many other sensors and converters.
|
||||
|
||||
The "Intel Non-Transparent Bridge support" driver supports PCIe hardware bridges which connect to systems. All writes to mapped memory will be mirrored on both systems.
|
||||
|
||||
"VME bridge support" is the same as above except the bridge uses VME which is a different bus standard.
|
||||
|
||||
"Pulse-Width Modulation (PWM) Support" controls the back-light and fan speed by regulating the average power received by such devices.
|
||||
|
||||
"IndustryPack bus support" offers drivers for the IndustryPack bus standards.
|
||||
|
||||
In the next article, we will configure the firmware drivers. Mahalo!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.linux.org/threads/the-linux-kernel-configuring-the-kernel-part-18.4896/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
@ -0,0 +1,111 @@
|
||||
戴文的Linux内核专题：22 配置内核 (18)
|
||||
================================================================================
|
||||
|
||||
|
||||
你好！准备好下一篇文章了么？在本篇中，我们将会讨论辅助屏幕。辅助显示是一些小的LCD屏幕；大多数小于或等于128x64。接着，我们会讨论用户空间IO驱动，一些虚拟驱动，Hyper-V，开发中驱动，IOMMU，和其他一些内核特性。
|
||||
|
||||
第一个配置辅助显示的驱动是"KS0108 LCD Controller"。KS0108 LCD Controller是由三星制造的图形控制器。
|
||||
|
||||
下面可以设置LCD并口地址(Parallel port where the LCD is connected)。第一个并口地址是0x378，下一个是0x278，第三个是0x3BC。这些不是地址唯一的选择。大多数人不需要改变这个。shell命令"cat /proc/ioports"会列出可用的并口和地址。
|
||||
|
||||
内核可以设置KS0108 LCD 控制器的写入延时到并口(Delay between each control writing (microseconds))。默认的值大部分是正确的，因此一般不需要更改。
|
||||
|
||||
"CFAG12864B LCD"屏幕是一块128x64，双色LCD屏幕。这块屏幕依赖于KS0108 LCD控制器。
|
||||
|
||||
可以改变这些LCD屏幕的刷新率(Refresh rate (hertz))。通常上，更高的刷新率会导致更多的CPU活动。这意味着一个缓慢的系统需要一个更低的刷新率。
|
||||
|
||||
设置完辅助显示后，接着设置"Userspace I/O drivers"。用户空间系统允许用户的应用和进程访问内核中断和内存地址。启用了它，一些驱动可以放在用户空间。
|
||||
|
||||
"generic Hilscher CIF Card driver"用于Profibus卡和Hilscher CIF卡。
|
||||
|
||||
"Userspace I/O platform driver"在用户空间创建通用驱动系统。
|
||||
|
||||
下一个驱动和上面的相同，但是增加IRQ处理(Userspace I/O platform driver with generic IRQ handling)。
|
||||
|
||||
下面的驱动又像前面的一个，但是增加了动态内存支持(Userspace platform driver with generic irq and dynamic memory)。
|
||||
|
||||
下面，是一些供应商/设备特性的驱动。
|
||||
|
||||
接着是一些通用PCI/PCIe卡驱动(Generic driver for PCI 2.3 and PCI Express cards)。
|
||||
|
||||
下面的驱动用于"VFIO support for PCI devices"。VFIO代表Virtual Function Input/Output(虚拟功能输入/输出)。VFIO允许设备直接以安全方式访问用户空间。
|
||||
|
||||
"VFIO PCI support for VGA devices"允许VGA通过VFIO被PCI支持。
|
||||
|
||||
接下来是virtio驱动。virtio是一个IO虚拟化平台。这个虚拟软件用于操作系统虚拟化。这在Linux系统上的虚拟机上运行一个操作系统时需要。
|
||||
|
||||
我们第一个可以配置的virtio驱动是"PCI driver for virtio devices"。这允许虚拟访问PCI
|
||||
|
||||
"Virtio balloon driver"允许虚拟系统的内存根据需要扩展或减少。通常上，没有人希望在需要内存的时候，虚拟系统保留它可能不会使用的内存。
|
||||
|
||||
下面的驱动允许内存映射到virtio设备(Platform bus driver for memory mapped virtio devices)。
|
||||
|
||||
如果Linux内核需要运行在微软的Hyper-V系统上，那么启用这个驱动(Microsoft Hyper-V client drivers)。这允许Linux能够成为Hyper的访客/客户端系统。
|
||||
|
||||
|
||||
|
||||
下面，我们会配置开发中的驱动。这些驱动人在开发当中，可能会变化很快，或者还没到Linux内核的质量标准。这个分类中的驱动只有Android驱动(在内核3.9.4中)。是的，Andorid使用Linux内核，这使得Andorid编程一个Linux系统。然而，这仍然有争议。如果内核是用于Android，那么最好启用所有的驱动。
|
||||
|
||||
"Android Binder IPC Driver"提供了对于Binder的支持，它允许Andorid系统进程间相互通信。
|
||||
|
||||
下面可以启用ashmen驱动(Enable the Anonymous Shared Memory Subsystem)。Ashmem代表"Anonymous SHared MEMory"(虚拟内存共享)或者"Android SHared MEMory"(Andorid共享内存)。
|
||||
|
||||
"Android log driver"提供了完整的Andorid日志系统。
|
||||
|
||||
"Timed output class driver" 和 "Android timed gpio driver"允许Andorid系统操作GIP引脚并在超时后取消操作。
|
||||
|
||||
"Android Low Memory Killer"会在需要更多内存关闭进程。这个特性会杀死不再使用或活跃的任务。
|
||||
|
||||
"Android alarm driver"使内核在设定的间隔后唤醒。
|
||||
|
||||
在配置晚开发中的驱动后，下面的驱动用于X86平台。这些驱动是 X86 (32-bit)的供应商/设备特定硬件。
|
||||
|
||||
下一个驱动是"Mailbox Hardware Support"。这个框架控制邮箱队列和硬件邮箱系统的中断信号。
|
||||
|
||||
"IOMMU Hardware Support"链接内存到能够使用DMA的设备上。IOMMU增强了DMA。IOMMU映射地址并阻止故障设备访问内存。IOMMU同样允许硬件访问比没有IOMMU更多内存。
|
||||
|
||||
"AMD IOMMU support"提供了对AMD设备更好的IOMMU支持。
|
||||
|
||||
对于AMD IOMMU支持存在调试特性(Export AMD IOMMU statistics to debugfs)。
|
||||
|
||||
存在一个对于AMD硬件的更新版本的IOMMU驱动(AMD IOMMU Version 2 driver)。
|
||||
|
||||
Linux内核同样支持对Intel设备的IOMMU驱动支持(Support for Intel IOMMU using DMA Remapping Devices)。
|
||||
|
||||
一些设备可能会接受不同的电压和时钟频率。这个驱动允许操作系统控制设备的电压输出和时钟频率(Generic Dynamic Voltage and Frequency Scaling (DVFS) support)。启用了这个驱动，可以启用下面的那些对于电源/性能管理特性。
|
||||
|
||||
"Simple Ondemand"就像上面的，但是只会基于设备活动改变时钟频率。通常上，更多的活动意味着设备需要更快的时钟速率来使用更多的资源需求。
|
||||
|
||||
"Performance"允许系统设置最高支持的时钟速度以满足最好的性能。这会增加电源消耗。
|
||||
|
||||
"Powersave"会设置时钟频率到最低以节约电源。
|
||||
|
||||
"Userspace"允许用户空间设置时钟频率。
|
||||
|
||||
"External Connector Class (extcon) support"使得用户空间可以监视外部连接器如USB和AC口。这允许应用了解是否插入了线缆。用户几乎都希望启用这个。如果任何人由于某个合理的理由禁用了它，请告诉我们为什么这么做。
|
||||
|
||||
"GPIO extcon support"驱动就像上面的驱动，但是它只对于GPIO管脚。
|
||||
|
||||
接下来是不同的供货商/设备特定的内存控制器(Memory Controller drivers)。内存芯片控制器可能是独立的设备或者内置在内存芯片上。这些控制器管理这输入和输出的数据流。
|
||||
|
||||
"Industrial I/O support"驱动提供了标准的传感器接口而不管总线的类型(像PCIe、spi、GPIO等等)。IIO是"Industrial I/O support"(工业IO)的通用缩写。
|
||||
|
||||
Linux内核提供了大量不同的加速器、放大器模数转换器、惯性测量单元、光敏传感器、磁场传感器和其他许多传感器和转换器的支持。
|
||||
|
||||
"Intel Non-Transparent Bridge support"驱动支持连接到系统的PCIe硬件桥。所有到映射内存的写入会镜像到两个系统中。
|
||||
|
||||
"VME bridge support"和上面的相同除了桥使用的是VME，这是一个不同的总线标准。
|
||||
|
||||
"Pulse-Width Modulation (PWM) Support"通过调节从这些设备收到的平均功率调节背光灯和风扇速度。
|
||||
|
||||
"IndustryPack bus support"提供了对IndustryPack总线标准的支持。
|
||||
|
||||
下一篇文章，我们会继续配置固件驱动。谢谢!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.linux.org/threads/the-linux-kernel-configuring-the-kernel-part-18.4896/
|
||||
|
||||
译者：[geekpi](https://github.com/geekpi) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
Loading…
Reference in New Issue
Block a user