tachyon device

Overview: Linux users often have difficulty identifying device names of the same type, such as eth0, eth1, sda, and sdb. By observing the kernel device names of these devices, users usually know what types of devices they want, but do not know which devices they want. For example, in a device name list filled with ephemeral disks and Fiber-Optic Disks (/dev/sd*),

Relationship between bus, device, and driver in Linux 1. Bus: As the connection channel between the host and peripherals, some buses are relatively standard and form many protocols. Such as PCI, USB, 1394, and IIC. Any device can select a suitable bus to connect to the host. Of course, the host may be the CPU itself. The memory is also connected to the host through the bus. The bus that can be used by the m

There are two main tasks for a device driver:1. Accessing the device's memory2. Interruption of processing equipmentFor the first task, the UIO core implements the Mmap () to handle the physical memory (physical memory), the logical RAM (logical memories),Virtual memory. UiO driver Writing is no need to consider these cumbersome details.For the second task, the answer to the device interrupt must be in kern

Http://blog.csdn.net/cglover/archive/2007/06/01/1634300.aspx Lost Device) Lost DeviceOne Microsoft? Direct3d? It can be in an operational or lost state. The operation status is the normal status of the device. The device runs as expected and present all rendering results. When an event occurs, if the full-screen application loses the keyboard i

An important feature of linux kernel is the provision of a unified kernel device model. With the continuous advancement of technology, the topology structure of the system becomes more and more complex, and the requirements for smart power management, hot swapping, and plugandplay support are also increasing, making it difficult to use 2.4 cores... an important feature of the linux 2.6 kernel is the provision of a unified kernel

As a driver author, you may find that you face a device that must download the firmware into it before it can support work. The competition in many parts of the hardware market is so strong that even a bit of the cost of the EEPROM used as a device control firmware is not willing to spend. So the firmware is advertised on a CD along with the hardware, and the operating system is responsible for transmitting

Overview: Linux users often find it difficult to identify the same type of device name, such as Eth0, Eth1, SDA, SDB, and so on. By observing the kernel device names of these devices, users usually know what type of device they are, but they don't know which device they want. For example, in a list of

Lost DeviceOne Microsoft? Direct3d? It can be in an operational or lost state. The operation status is the normal status of the device. The device runs as expected and present all rendering results. When an event occurs, if the full-screen application loses the keyboard input focus, the device changes to the lost State, resulting in rendering failure. The loss st

This article from Csdn Blog, reproduced please indicate the source: http://blog.csdn.net/aaa6695798/archive/2009/11/06/4776202.aspx 　　 This part of all the structure of the Declaration can be found in the kernel source file usb.h, interested friends can read the source code. USB devices are complex, but the Linux kernel provides a subsystem called USB core to handle most of the complex work, so this is what is described here as the interface between the driver and the USB core. In the USB

There are two main tasks for a device driver:1. Accessing the device's memory2. Interruption of processing equipmentFor the first task. The UIO core implements the Mmap () capable of handling physical memory (physical memory), logical (logicalVirtual memory. The UiO drive is written without the need to consider these tedious details.For the second task, the answer to the device interrupt must be in kernel s

Equipment for data, driven for processing1, take led-s3c24xx.c as an example to analyze the registration process of platform device and driverthe driving data structure of the LEDs is as follows:static struct Platform_driver S3c24xx_led_driver = {. probe= s3c24xx_led_probe,.remove= s3c24xx_led_remove,.driver= {.Name= "s3c24xx_led",. owner= this_module,},};struct platform_driver data structure is struct Platform_driver {int (*probe) (struct Platform_de

The following is an article I recently read when I wrote a pci driver. I hope it will be helpful to you. Hi, I was a beginner in linux.The driver is also difficult, and many people are asked about it shamelessly. I would like to express my gratitude and sorry to these experts, especially unix1998. The level of helplessness is limited. It may be wrong in some places. IfIf you are not reading the original text smoothly, read the original text.Original article:/Documentation/pci.txtThere is also a