For linux driver development you can start by reading “Linux Device Drivers, Third Edition” pdf.
It is free and give you an idea about how everything works.
The real learning is by reading and using the linux kernel api doc or directly the source code of the api you want to call.
Source : i did this for a school project where i had to implement multiple kernel modules.
I think the real issue with driver development is that almost nobody ever has a reason to do it. It’s a much more constrained way of programming compared to normal programs, and isn’t necessary unless you need to talk to hardware or something. So, nobody has an excuse to learn it.
For linux driver development you can start by reading “Linux Device Drivers, Third Edition” pdf.
It is free and give you an idea about how everything works.
The real learning is by reading and using the linux kernel api doc or directly the source code of the api you want to call.
Source : i did this for a school project where i had to implement multiple kernel modules.
Neat! I’ll add it to my long list of things ADHD will never let me finish!
I think the real issue with driver development is that almost nobody ever has a reason to do it. It’s a much more constrained way of programming compared to normal programs, and isn’t necessary unless you need to talk to hardware or something. So, nobody has an excuse to learn it.
… Unless you want to talk to hardware. Or something.
Yes… as I said. But, most people use hardware provided by other people, which means other people write the drivers.
Yes, and those people are people.
Also, sometimes the drivers are total garbage, and other people have to rewrite the garbage from the first people.
Also also, sometimes there is no driver.