Device drivers literally drive everything you're interested in--disks, monitors, keyboards, modems--everything outside the computer chip and memory. And writing device drivers is one of the few areas of programming for the Linux operating system that calls for unique, Linux-specific knowledge. For years now, programmers have relied on the classic Linux Device Drivers from O'Rei...
Device drivers literally drive everything you're interested in--disks, monitors, keyboards, modems--everything outside the computer chip and memory. And writing device drivers is one of the few areas of programming for the Linux operating system that calls for unique, Linux-specific knowledge. For years now, programmers have relied on the classic Linux Device Drivers from O'Reilly to master this critical subject. Now in its third edition, this bestselling guide provides all the information you'll need to write drivers for a wide range of devices. Over the years the book has helped countless programmers learn: * how to support computer peripherals under the Linux operating system * how to develop and write software for new hardware under Linux * the basics of Linux operation even if they are not expecting to write a driver The new edition of Linux Device Drivers is better than ever. The book covers all the significant changes to Version 2.6 of the Linux kernel, which simplifies many activities, and contains subtle new features that can make a driver both more efficient and more flexible. Readers will find new chapters on important types of drivers not covered previously, such as consoles, USB drivers, and more. Best of all, you don't have to be a kernel hacker to understand and enjoy this book. All you need is an understanding of the C programming language and some background in Unix system calls. And for maximum ease-of-use, the book uses full-featured examples that you can compile and run without special hardware. Today Linux holds fast as the most rapidly growing segment of the computer market and continues to win over enthusiastic adherents in many application areas. With this increasing support, Linux is now absolutely mainstream, and viewed as a solid platform for embedded systems. If you're writing device drivers, you'll want this book. In fact, you'll wonder how drivers are ever written without it.
作者简介
· · · · · ·
Jonathan Corbet got his first look at the BSD Unix source back in 1981, when an instructor at the University of Colorado let him "fix" the paging algorithm. He has been digging around inside every system he could get his hands on ever since, working on drivers for VAX, Sun, Ardent, and x86 systems on the way. He got his first Linux system in 1993, and has never looked back. Mr....
Jonathan Corbet got his first look at the BSD Unix source back in 1981, when an instructor at the University of Colorado let him "fix" the paging algorithm. He has been digging around inside every system he could get his hands on ever since, working on drivers for VAX, Sun, Ardent, and x86 systems on the way. He got his first Linux system in 1993, and has never looked back. Mr. Corbet is currently the co-founder and executive editor of Linux Weekly News (http://LWN.net/); he lives in Boulder, Colorado with his wife and two children.
Alessandro installed Linux 0.99.14 soon after getting his degree as electronic engineer. He then received a Ph.D. in computer science at the University of Pavia despite his aversion toward modern technology. He left the University after getting his Ph.D. because he didn't want to write articles. He now works as a free lancer writing device drivers and, um...articles. He used to be a young hacker before his babies were born; he's now an old advocate of Free Software who developed a bias for non-PC computer platforms.
Greg Kroah-Hartman has been writing Linux kernel drivers since 1999, and is currently the maintainer for the USB, PCI, I2C, driver core, and sysfs kernel subsystems. He is also the maintainer of the udev and hotplug userspace programs, as well as being a Gentoo kernel maintainer, ensuring that his email inbox is never empty. He is a contributing editor to Linux Journal Magazine, and works for IBM's Linux Technology Center, doing various Linux kernel related tasks.
目录
· · · · · ·
Preface
Jon's Introduction
Alessandro's Introduction
Greg's Introduction
Audience for This Book
Organization of the Material
· · · · · ·
(更多)
Preface
Jon's Introduction
Alessandro's Introduction
Greg's Introduction
Audience for This Book
Organization of the Material
Background Information
Online Version and License
Conventions Used in This Book
Using Code Examples
We'd Like to Hear from You
Safari Enabled
Acknowledgments
1. An Introduction to Device Drivers
1.1. The Role of the Device Driver
1.2. Splitting the Kernel
1.3. Classes of Devices and Modules
1.4. Security Issues
1.5. Version Numbering
1.6. License Terms
1.7. Joining the Kernel Development Community
1.8. Overview of the Book
2. Building and Running Modules
2.1. Setting Up Your Test System
2.2. The Hello World Module
2.3. Kernel Modules Versus Applications
2.4. Compiling and Loading
2.5. The Kernel Symbol Table
2.6. Preliminaries
2.7. Initialization and Shutdown
2.8. Module Parameters
2.9. Doing It in User Space
2.10. Quick Reference
3. Char Drivers
3.1. The Design of scull
3.2. Major and Minor Numbers
3.3. Some Important Data Structures
3.4. Char Device Registration
3.5. open and release
3.6. scull's Memory Usage
3.7. read and write
3.8. Playing with the New Devices
3.9. Quick Reference
4. Debugging Techniques
4.1. Debugging Support in the Kernel
4.2. Debugging by Printing
4.3. Debugging by Querying
4.4. Debugging by Watching
4.5. Debugging System Faults
4.6. Debuggers and Related Tools
5. Concurrency and Race Conditions
5.1. Pitfalls in scull
5.2. Concurrency and Its Management
5.3. Semaphores and Mutexes
5.4. Completions
5.5. Spinlocks
5.6. Locking Traps
5.7. Alternatives to Locking
5.8. Quick Reference
6. Advanced Char Driver Operations
6.1. ioctl
6.2. Blocking I/O
6.3. poll and select
6.4. Asynchronous Notification
6.5. Seeking a Device
6.6. Access Control on a Device File
6.7. Quick Reference
7. Time, Delays, and Deferred Work
7.1. Measuring Time Lapses
7.2. Knowing the Current Time
7.3. Delaying Execution
7.4. Kernel Timers
7.5. Tasklets
7.6. Workqueues
7.7. Quick Reference
8. Allocating Memory
8.1. The Real Story of kmalloc
8.2. Lookaside Caches
8.3. get_free_page and Friends
8.4. vmalloc and Friends
8.5. Per-CPU Variables
8.6. Obtaining Large Buffers
8.7. Quick Reference
9. Communicating with Hardware
9.1. I/O Ports and I/O Memory
9.2. Using I/O Ports
9.3. An I/O Port Example
9.4. Using I/O Memory
9.5. Quick Reference
10. Interrupt Handling
10.1. Preparing the Parallel Port
10.2. Installing an Interrupt Handler
10.3. Implementing a Handler
10.4. Top and Bottom Halves
10.5. Interrupt Sharing
10.6. Interrupt-Driven I/O
10.7. Quick Reference
11. Data Types in the Kernel
11.1. Use of Standard C Types
11.2. Assigning an Explicit Size to Data Items
11.3. Interface-Specific Types
11.4. Other Portability Issues
11.5. Linked Lists
11.6. Quick Reference
12. PCI Drivers
12.1. The PCI Interface
12.2. A Look Back: ISA
12.3. PC/104 and PC/104+
12.4. Other PC Buses
12.5. SBus
12.6. NuBus
12.7. External Buses
12.8. Quick Reference
13. USB Drivers
13.1. USB Device Basics
13.2. USB and Sysfs
13.3. USB Urbs
13.4. Writing a USB Driver
13.5. USB Transfers Without Urbs
13.6. Quick Reference
14. The Linux Device Model
14.1. Kobjects, Ksets, and Subsystems
14.2. Low-Level Sysfs Operations
14.3. Hotplug Event Generation
14.4. Buses, Devices, and Drivers
14.5. Classes
14.6. Putting It All Together
14.7. Hotplug
14.8. Dealing with Firmware
14.9. Quick Reference
15. Memory Mapping and DMA
15.1. Memory Management in Linux
15.2. The mmap Device Operation
15.3. Performing Direct I/O
15.4. Direct Memory Access
15.5. Quick Reference
16. Block Drivers
16.1. Registration
16.2. The Block Device Operations
16.3. Request Processing
16.4. Some Other Details
16.5. Quick Reference
17. Network Drivers
17.1. How snull Is Designed
17.2. Connecting to the Kernel
17.3. The net_device Structure in Detail
17.4. Opening and Closing
17.5. Packet Transmission
17.6. Packet Reception
17.7. The Interrupt Handler
17.8. Receive Interrupt Mitigation
17.9. Changes in Link State
17.10. The Socket Buffers
17.11. MAC Address Resolution
17.12. Custom ioctl Commands
17.13. Statistical Information
17.14. Multicast
17.15. A Few Other Details
17.16. Quick Reference
18. TTY Drivers
18.1. A Small TTY Driver
18.2. tty_driver Function Pointers
18.3. TTY Line Settings
18.4. ioctls
18.5. proc and sysfs Handling of TTY Devices
18.6. The tty_driver Structure in Detail
18.7. The tty_operations Structure in Detail
18.8. The tty_struct Structure in Detail
18.9. Quick Reference
19. Bibliography
19.1. Books
19.2. Web Sites
Index
· · · · · · (收起)
GFP_ATOMIC
Used to allocate memory from interrupt handlers and other code outside of a process context. Never sleeps.
GFP_KERNEL
Normal allocation of kernel memory. May sleep. (查看原文)
struct gendisk is a dynamically allocated structure that requires special kernel
manipulation to be initialized; drivers cannot allocate the structure on their own.
Instead, you must call: (查看原文)
0 有用 optman 2014-04-22 16:58:44
生吞活剥,硬是翻完了。帮助我理解了很多概念,特别是很少书涉及的PCI资源分配等硬件相关内容。本书细节很多,可以作为Linux驱动开发的API参考手册。要想真正理解某个子系统的概念,还是需要找专著,这本讲得太过泛泛。
0 有用 花开花落她是谁 2023-08-16 11:19:27 美国
看了一点点,暂时放弃
0 有用 一瓢之饮 2020-06-22 16:07:01
读了几个需要的章节
0 有用 西东东西 2014-05-04 21:59:38
经典ldd, 驱动开发必备no.1
0 有用 nwind 2015-10-31 10:41:28
需要的时候翻一下
0 有用 花开花落她是谁 2023-08-16 11:19:27 美国
看了一点点,暂时放弃
0 有用 squirrel-prog 2023-03-03 09:51:52 江苏
读英文原版. 读英文原版. 读英文原版. 重要的事情说三遍.
0 有用 ansondeng 2021-09-03 09:32:56
十年之后的重读。第一次真的没弄懂什么。
0 有用 Terenceli 2021-01-23 15:49:25
当我在虚拟化领域把整个计算机架构搞清楚再重读此书,很多东西变得很清晰。
0 有用 六个九十度 2020-12-01 16:57:11
插图太少,示例代码的命名过于简略,有些设计思想解释得生硬,但至少内容全面,且介绍很多api的应用场景、注意事项什么的,适合当工具书查阅。驱动模型和内存映射两章很不错。