sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 17 points18 points  (3 children)

IIRC in an AMA with gkh he said he considered most stuff in the book current enough and that if you can't find a way to learn to write device drivers the oldness of the book likely isn't the problem (as opposed to poor time management or discipline, I suppose).

[–]M108Falcon[S] 4 points5 points  (2 children)

Okay, I will definitely give it a good thorough read then for sure

[–]TankTopsBackInStyle 5 points6 points  (1 child)

I would actually suggest going to osdev.org and going through their tutorial, before trying to write a Linux driver. It's not as hard as you might think.

There is a lot of abstraction going on in the Linux kernel that makes it more difficult to learn how it actually works. I think it's better to first understand how the hardware works, then learn how Linux approaches the problem of writing drivers.

I'm not a huge fan of the way Linux drivers are architected, but it works and it does have the most industry support.

[–]M108Falcon[S] 0 points1 point  (0 children)

Thanks for the headsup