#452 in Computers & technology books
Use arrows to jump to the previous/next product

Reddit mentions of Linux Device Drivers, 3rd Edition

Sentiment score: 6
Reddit mentions: 10

We found 10 Reddit mentions of Linux Device Drivers, 3rd Edition. Here are the top ones.

Linux Device Drivers, 3rd Edition
Buying options
View on Amazon.com
or
O Reilly Media
Specs:
Height9.19 Inches
Length7 Inches
Number of items1
Release dateFebruary 2005
Weight2.2156457331 Pounds
Width1.3 Inches

idea-bulb Interested in what Redditors like? Check out our Shuffle feature

Shuffle: random products popular on Reddit

Found 10 comments on Linux Device Drivers, 3rd Edition:

u/EirrinGoBragh · 5 pointsr/linux

Read here: http://www.advancedlinuxprogramming.com/


Program. Then read here: http://www.amazon.com/Linux-Kernel-Development-3rd-Edition/dp/0672329468


Program some more. Then maybe read here: http://www.amazon.com/Linux-Device-Drivers-3rd-Edition/dp/0596005903


And program some more. Yes, I know two of the links are to amazon. I'm sure if you look real hard you can find other formats.

u/Enlightenment777 · 4 pointsr/math

What file name format do you use for your ebooks?

Mine is...

Format:
<title><edition><year><isbn><optional famous authors names>.<ext>

Example:
Linux Device Drivers_3rd Ed_2005_9780596005900.pdf
http://www.amazon.com/Linux-Device-Drivers-Jonathan-Corbet/dp/0596005903/ref=sr_1_1?ie=UTF8&s=books&qid=1278407654&sr=1-1

I rarely include the authors name, except for famous or favorite authors.

In recent years, I always use the ISBN-13, but remove all dashes and spaces.

I always use underscores between 'fields' in ALL of my file names to make it easier to parse into a database.

As long as you include the exact ISBN, you can always look up the publisher and author, thus is why I don't include either one in my file names any more.

u/the_gnarts · 4 pointsr/linux

> Wow, that's really great. Where do you even start to learn to program this kind of thing? Like accessing hardware

This: https://www.amazon.com/dp/0596005903/ should cover most of it.

u/c0nv0luti0n · 3 pointsr/embedded

I second freeRTOS. Pick up an Atmel dev board. They have good support for freeRTOS. Big concepts here will be stack management, mutex/semaphores for thread safe operations, using message queues to communicate between threads, blocking/non blocking operations, and find a profiler so you can visualize your efficiency.

For driver development I will point you towards Linux. Try writing a basic storage or GPIO driver on a raspberry pi. I have linked a book below that will help with understanding Linux drivers. The big thing is you will have to use ioctl calls to communicate with your driver.
Link to book!

u/daniel48 · 2 pointsr/linux

You're one of the coauthors of Linux Device Drivers, published in 2005... Are there any plans of releasing a more organized, updated edition? Would you recommend any other texts for programmers wanting to learn driver development?

u/AlienBloodMusic · 2 pointsr/linux

The OS is just a program like any other program. In order to really start understanding how it works, you should learn C.

Once you've got some C down, read Advanced Linux Programming

From there read Robert Loves Linux Kernel Development - even if you're not a kernel developer, it'll give you tremendous insight into how the kernel works.

Also check out Linux Device Drivers. I found this & Loves book complemented each other nicely.

u/ChuckMauriceFacts · 2 pointsr/france

> Dévs Embarqués Linux

Hey mais c'est moi ? enfin... ça aurait dû.

Vu que j'ai appris Linux sur le tas, j'ai pas forcément les bonnes ressources, et maintenant je ponctue mes connaissances de base par des recherches Google. Mais j'ai retenu quelques trucs :

  • https://linuxjourney.com/

  • Rien que le tutoriel d'installation d'ArchLinux m'en avait appris beaucoup à l'époque, notamment sur tout ce qui est réseau et périphériques

  • La bible du développeur embarqué Linux (même si j'en ai oublié la plupart).

  • J'ai demandé à un pote Sysadmin et il m'a dit que cette formation Red Hat (gratuite) était pas mal, et que maitriser Red Hat et Debian de fond en comble c'était obligatoire en entreprise.

    Mais je trouve que je n'apprends bien qu'à travers des projets, même quand je les commence à l'arrache sans rien savoir, donc je ne peux que te conseiller de te faire des petits projets perso (un serveur de partage de fichiers ? une caméra qui stream sur un réseau ? un miroir connecté ?). C'est basiquement à ça que me servent mes cartes RPi et assimilées maintenant.

    Discussion du Mercredi Tech sur les certifs car j'y connais rien.
u/dinosaurdev · 1 pointr/cscareerquestions

This one stands out: http://www.amazon.com/Linux-Device-Drivers-3rd-Edition/dp/0596005903

Eh, I honestly don't use a book anymore. It's just ingrained knowledge now. From reading that book, various classes and labs on computer architecture and operating systems. Now I just google for a specific thing / looking at man pages on my terminal.

u/Parzeval · 1 pointr/cprogramming

Shit, sorry for not replying sooner, I just saw this response - I don't check on here very much.

Thanks for the reply, I'd given up on this thread. I'll look into those resources you mention. The target OS is Linux, so that makes things a bit simpler i guess.

Do you have any opinion on the relative merits of these 3 driver books: (I've heard the bottom one 'Essential Linux Device Drivers' is getting a bit old now (targets a fairly old kernel) but I don't know if that matters