ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
is anyone else reading this book "linux device drivers" on there way to (trying) to become a kernel hacker? what kind of stuff are you doing to "practice" what you learn? i usually find myself getting lost in various directories like /usr/src/linux/kernel or /usr/src/linux/fs, but i really dont write much kernel code. mostly i just make sure i 100% understand all the example book code, but im already on the 7th chapter and have yet to do a real "project". when i was reading stevens books i always had more ideas of progs to write than time to write them.. but now it's just kinda reading and reading. wondering if anyone else is or was in a similar position? the only ideas i really have of stuff to do is going thru various kernel code and commenting the hell out of it, just making sure i understand how it works, that's about all i've accomplished other than just reading.. so what is the rest of you guys are doing??
hey infamous41md - i kinda reached the 2nd chapter. and stopped.
i know for certain that the guy who started work on the prismGT wireless card driver used this as a starting point.
maybe you can take up some new/less-heard-of piece of hardware that no ones written a driver for yet, and start a project?
yea i've been by kernelnewbies more than a few times, it is a cool site so thanks anyways. i've never checked out the IRC channel tho, maybe i'll swing by there sometime.
h/w: you should keep going ... those first 2 chapters were painful, damn painful, i must of read them a dozen times, but after taht it gets alot easier. once it all "clicks" it's really interesting. i would like to write a real driver, but the problem is the book doesnt even touch on real hardware until chapter 9 i think. so far all the "devices" just act on memory.
I thought that was a pretty good book. I have to say I didn't read it cover to cover. But the first time I wrote a device driver I read several sections of it as I went along to figure out how to do things. It has made a good reference since then when I forget the syntax of a function. These days I find myself haven't right device drivers a lot less often though, because so much is supported already.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.