The Linux Kernel Module Programming Guide

In my opinion the best way to do kernel development is to just look at device drivers in kernel sources, study what current drivers do and write your own driver. The kernel supports su much heterogeneous devices and its APIs change continuously that it is practically impossible to write a complete guide on this topic.

Just a warning if you do embedded work with Linux (RPi, Beaglebone, etc)... this guide doesn't cover the Devicetree APIs. Doesn't even acknowledge their existence.

See also: <a href="https:&#x2F;&#x2F;0xax.gitbooks.io&#x2F;linux-insides&#x2F;" rel="nofollow">https:&#x2F;&#x2F;0xax.gitbooks.io&#x2F;linux-insides&#x2F;</a>

Not sure if the eating555 is the author or whether the author is watching this thread...<p>This is awesome.. my only comment is the first thing I went to do was to copy and paste the code blocks and found end of line whitespace and double line breaks were included (presumably for the line numbering etc.)<p>e.g.<p>sudo apt-get update<p>apt-cache search linux-headers-`uname -r`

A semi-related question: do kernel modules play nicely with device-tree instantiations?<p>Like let&#x27;s say I wanted to instantiate an I2C with a custom driver in my device-tree. Can I put the controller&#x27;s driver in a kernel module that lives in &#x2F;lib&#x2F;modules? Or do I need to compile it into the kernel?

Tried to make text size larger at <a href="https:&#x2F;&#x2F;sysprog21.github.io&#x2F;lkmpg&#x2F;" rel="nofollow">https:&#x2F;&#x2F;sysprog21.github.io&#x2F;lkmpg&#x2F;</a> and could not, it stays fixed. It would be great to fix this problem.

Would I be out of line in suggesting DKMS to be used?<p>I figure it would be close to mandatory for anyone who wanted to distribute their module to others, without having to tell them to rebuild every time their kernel changed.

can you update the Makefile so it generate a PDF only? Also, the &quot;make all&quot; doesn&#x27;t seems to be working as expected here. Probably missing some dependency.