深入学习Linux驱动开发：英文版PDF

需积分: 9 179 浏览量更新于2024-07-26 收藏 7.4MB PDF 举报

"Linux Device Drivers 3rd-Edition.pdf 是一本关于Linux驱动开发的英文文档，适合想要深入理解Linux内核机制和驱动程序开发的读者。该文档可能涵盖了从基础概念到高级技术的各种主题，旨在帮助读者掌握如何为Linux系统编写设备驱动。O'Reilly出版社还提供了其他与Linux和Unix相关的书籍资源，包括样本章节和代码示例，可以在linux.oreilly.com找到。此外，ONLamp.com是一个专注于开源网络平台——Linux、Apache、MySQL以及Perl、Python或PHP的网站。O'Reilly还组织各种会议，聚集创新者分享最新的工具和系统知识。对于程序员和IT专业人员，Safari Bookshelf在线参考图书馆提供超过1000本书的搜索功能，订阅者可以迅速找到关键问题的答案。" 在《Linux Device Drivers》这本书中，你可能会学到以下关键知识点： 1. **Linux内核架构**：了解Linux内核的基础结构，包括进程管理、内存管理、中断处理、调度算法等核心概念。 2. **驱动程序分类**：学习字符设备驱动、块设备驱动和网络设备驱动的区别及其各自的工作原理。 3. **设备模型**：熟悉Linux设备模型，包括总线、设备、驱动之间的关系，以及udev设备管理系统。 4. **内核模块编程**：如何编写和加载内核模块，以及模块的生命周期管理。 5. **I/O操作**：理解I/O端口、DMA（直接存储器访问）以及中断处理，以及如何在驱动程序中实现它们。 6. **设备文件系统（devfs, udev）**：如何通过这些系统来创建和管理设备节点。 7. **内存管理**：学习如何在驱动程序中高效地使用内存，包括物理内存和虚拟内存的分配与释放。 8. **同步与互斥**：理解信号量、自旋锁、读写锁等同步机制，防止数据竞争和死锁。 9. **中断处理**：学习中断处理程序的编写，包括软中断和硬件中断的区别。 10. **PCI和USB设备驱动**：针对这些常见总线的设备编写驱动的特殊考虑。 11. **字符设备驱动编程**：了解如何为字符设备编写驱动，如串口、并口、键盘和鼠标等。 12. **块设备驱动编程**：如何为硬盘、闪存等块设备编写驱动，包括缓冲策略和I/O调度。 13. **网络设备驱动**：学习网络协议栈，以及如何编写网络接口卡的驱动。 14. **调试技巧**：使用gdb、kdb等工具进行内核级调试，以及日志记录和故障排查方法。 15. **电源管理**：了解如何在驱动中实现电源管理和低功耗模式。通过阅读这本书，开发者将能够深入理解Linux内核的工作方式，并具备开发和维护Linux设备驱动的能力，这对于任何希望在嵌入式系统、服务器或桌面环境中工作的人来说都是至关重要的。同时，O'Reilly的其他相关资源和在线服务可以提供额外的学习支持和实时解答问题的途径。

This is the Title of the Book, eMatter Edition

xvi

Preface

Pay special attention to notes set apart from the text with the following icons:

This is a tip. It contains useful supplementary information about the

topic at hand.

This is a warning. It helps you solve and avoid annoying problems.

Using Code Examples

This book is here to help you get your job done. In general, you may use the code in

this book in your programs and documentation. The code samples are covered by a

dual BSD/GPL license.

We appreciate, but do not require, attribution. An attribution usually includes the

title, author, publisher, and ISBN. For example: “Linux Device Drivers, Third Edi-

tion, by Jonathan Corbet, Alessandro Rubini, and Greg Kroah-Hartman. Copyright

2005 O’Reilly Media, Inc., 0-596-00590-3.”

We’d Like to Hear from You

Please address comments and questions concerning this book to the publisher:

O’Reilly Media, Inc.

1005 Gravenstein Highway North

Sebastopol, CA 95472

(800) 998-9938 (in the United States or Canada)

(707) 829-0515 (international or local)

(707) 829-0104 (fax)

We have a web page for this book, where we list errata, examples, and any addi-

tional information. You can access this page at:

http://www.oreilly.com/catalog/linuxdrive3

To comment or ask technical questions about this book, send email to:

bookquestions@oreilly.com

For more information about our books, conferences, Resource Centers, and the

O’Reilly Network, see our web site at:

http://www.oreilly.com

,ch00.11770 Page xvi Thursday, January 27, 2005 12:11 PM

This is the Title of the Book, eMatter Edition

Preface

xvii

Safari Enabled

When you see a Safari® Enabled icon on the cover of your favorite tech-

nology book, that means the book is available online through the

O’Reilly Network Safari Bookshelf.

Safari offers a solution that’s better than e-books. It’s a virtual library that lets you

easily search thousands of top tech books, cut and paste code samples, download

chapters, and find quick answers when you need the most accurate, current informa-

tion. Try it for free at http://safari.oreilly.com.

Acknowledgments

This book, of course, was not written in a vacuum; we would like to thank the many

people who have helped to make it possible.

Thanks to our editor, Andy Oram; this book is a vastly better product as a result of

his efforts. And obviously we owe a lot to the smart people who have laid the philo-

sophical and practical foundations of the current free software renaissance.

The first edition was technically reviewed by Alan Cox, Greg Hankins, Hans Ler-

men, Heiko Eissfeldt, and Miguel de Icaza (in alphabetic order by first name). The

technical reviewers for the second edition were Allan B. Cruse, Christian Morgner,

Jake Edge, Jeff Garzik, Jens Axboe, Jerry Cooperstein, Jerome Peter Lynch, Michael

Kerrisk, Paul Kinzelman, and Raph Levien. Reviewers for the third edition were

Allan B. Cruse, Christian Morgner, James Bottomley, Jerry Cooperstein, Patrick

Mochel, Paul Kinzelman, and Robert Love. Together, these people have put a vast

amount of effort into finding problems and pointing out possible improvements to

our writing.

Last but certainly not least, we thank the Linux developers for their relentless work.

This includes both the kernel programmers and the user-space people, who often get

forgotten. In this book, we chose never to call them by name in order to avoid being

unfair to someone we might forget. We sometimes made an exception to this rule

and called Linus by name; we hope he doesn’t mind.

Jon

I must begin by thanking my wife Laura and my children Michele and Giulia for fill-

ing my life with joy and patiently putting up with my distraction while working on

this edition. The subscribers of LWN.net have, through their generosity, enabled

much of this work to happen. The Linux kernel developers have done me a great ser-

vice by letting me be a part of their community, answering my questions, and setting

me straight when I got confused. Thanks are due to readers of the second edition of

this book whose comments, offered at Linux gatherings over much of the world,

,ch00.11770 Page xvii Thursday, January 27, 2005 12:11 PM

This is the Title of the Book, eMatter Edition

xviii

Preface

have been gratifying and inspiring. And I would especially like to thank Alessandro

Rubini for starting this whole exercise with the first edition (and staying with it

through the current edition); and Greg Kroah-Hartman, who has brought his consid-

erable skills to bear on several chapters, with great results.

Alessandro

I would like to thank the people that made this work possible. First of all, the incred-

ible patience of Federica, who went as far as letting me review the first edition dur-

ing our honeymoon, with a laptop in the tent. I want to thank Giorgio and Giulia,

who have been involved in later editions of the book and happily accepted to be sons

of “a gnu” who often works late in the night. I owe a lot to all the free-software

authors who actually taught me how to program by making their work available for

anyone to study. But for this edition, I’m mostly grateful to Jon and Greg, who have

been great mates in this work; it couldn’t have existed without each and both of

them, as the code base is bigger and tougher, while my time is a scarcer resource,

always contended for by clients, free software issues, and expired deadlines. Jon has

been a great leader for this edition; both have been very productive and technically

invaluable in supplementing my small-scale and embedded view toward program-

ming with their expertise about SMP and number crunchers.

Greg

I would like to thank my wife Shannon and my children Madeline and Griffin for

their understanding and patience while I took the time to work on this book. If it

were not for their support of my original Linux development efforts, I would not be

able to do this book at all. Thanks also to Alessandro and Jon for offering to let me

work on this book; I am honored that they let me participate in it. Much gratitude is

given to all of the Linux kernel programmers, who were unselfish enough to write

code in the public view, so that I and others could learn so much from just reading it.

Also, for everyone who has ever sent me bug reports, critiqued my code, and flamed

me for doing stupid things, you have all taught me so much about how to be a better

programmer and, throughout it all, made me feel very welcome to be part of this

community. Thank you.

,ch00.11770 Page xviii Thursday, January 27, 2005 12:11 PM

This is the Title of the Book, eMatter Edition

Chapter 1

CHAPTER 1

An Introduction to

Device Drivers

One of the many advantages of free operating systems, as typified by Linux, is that

their internals are open for all to view. The operating system, once a dark and myste-

rious area whose code was restricted to a small number of programmers, can now be

readily examined, understood, and modified by anybody with the requisite skills.

Linux has helped to democratize operating systems. The Linux kernel remains a

large and complex body of code, however, and would-be kernel hackers need an

entry point where they can approach the code without being overwhelmed by com-

plexity. Often, device drivers provide that gateway.

Device drivers take on a special role in the Linux kernel. They are distinct “black

boxes” that make a particular piece of hardware respond to a well-defined internal

programming interface; they hide completely the details of how the device works.

User activities are performed by means of a set of standardized calls that are indepen-

dent of the specific driver; mapping those calls to device-specific operations that act

on real hardware is then the role of the device driver. This programming interface is

such that drivers can be built separately from the rest of the kernel and “plugged in”

at runtime when needed. This modularity makes Linux drivers easy to write, to the

point that there are now hundreds of them available.

There are a number of reasons to be interested in the writing of Linux device drivers.

The rate at which new hardware becomes available (and obsolete!) alone guarantees

that driver writers will be busy for the foreseeable future. Individuals may need to

know about drivers in order to gain access to a particular device that is of interest to

them. Hardware vendors, by making a Linux driver available for their products, can

add the large and growing Linux user base to their potential markets. And the open

source nature of the Linux system means that if the driver writer wishes, the source

to a driver can be quickly disseminated to millions of users.

This book teaches you how to write your own drivers and how to hack around in

related parts of the kernel. We have taken a device-independent approach; the pro-

gramming techniques and interfaces are presented, whenever possible, without being

tied to any specific device. Each driver is different; as a driver writer, you need to

,ch01.2168 Page 1 Thursday, January 20, 2005 9:21 AM

This is the Title of the Book, eMatter Edition

Chapter 1: An Introduction to Device Drivers

understand your specific device well. But most of the principles and basic tech-

niques are the same for all drivers. This book cannot teach you about your device,

but it gives you a handle on the background you need to make your device work.

As you learn to write drivers, you find out a lot about the Linux kernel in general;

this may help you understand how your machine works and why things aren’t

always as fast as you expect or don’t do quite what you want. We introduce new

ideas gradually, starting off with very simple drivers and building on them; every new

concept is accompanied by sample code that doesn’t need special hardware to be

tested.

This chapter doesn’t actually get into writing code. However, we introduce some

background concepts about the Linux kernel that you’ll be glad you know later,

when we do launch into programming.

The Role of the Device Driver

As a programmer, you are able to make your own choices about your driver, and

choose an acceptable trade-off between the programming time required and the flexi-

bility of the result. Though it may appear strange to say that a driver is “flexible,” we

like this word because it emphasizes that the role of a device driver is providing

mechanism, not policy.

The distinction between mechanism and policy is one of the best ideas behind the

Unix design. Most programming problems can indeed be split into two parts: “what

capabilities are to be provided” (the mechanism) and “how those capabilities can be

used” (the policy). If the two issues are addressed by different parts of the program,

or even by different programs altogether, the software package is much easier to

develop and to adapt to particular needs.

For example, Unix management of the graphic display is split between the X server,

which knows the hardware and offers a unified interface to user programs, and the

window and session managers, which implement a particular policy without know-

ing anything about the hardware. People can use the same window manager on dif-

ferent hardware, and different users can run different configurations on the same

workstation. Even completely different desktop environments, such as KDE and

GNOME, can coexist on the same system. Another example is the layered structure

of TCP/IP networking: the operating system offers the socket abstraction, which

implements no policy regarding the data to be transferred, while different servers are

in charge of the services (and their associated policies). Moreover, a server like ftpd

provides the file transfer mechanism, while users can use whatever client they prefer;

both command-line and graphic clients exist, and anyone can write a new user inter-

face to transfer files.

Where drivers are concerned, the same separation of mechanism and policy applies.

The floppy driver is policy free—its role is only to show the diskette as a continuous

,ch01.2168 Page 2 Thursday, January 20, 2005 9:21 AM

剩余631页未读，继续阅读

翩翩好少年

粉丝: 5
资源: 2

深入学习Linux驱动开发：英文版PDF

linux device driver\ldd3英文版附源码.rar

Linux Device Drivers 3rd Edition.pdf_LinuxDeviceDrivers_

Linux.Device.Drivers.3rd.Edition.Feb.2005.eBook-DDU.chm

Oreilly-linux-device-drivers-3rd-edition-feb-2005._LDD 3rd editi

linux device drivers 3rd edition-English edition

Linux Device Driver 3rd Edition.pdf

linux device drivers 3rd edition pdf

Linux Device Drivers 3rd Edition

Linux DeviceDrivers 3rd Edition

kernel\Linux Device Drivers 3rd Edition

最新资源