I am starting to read a book on device drivers, and an example given to get started is:

#define MODULE
#include <linux/module.h>
//some stuff here

It gives errors for module.h. But how could module.h have errors if it's worked for everybody else? What do I need to do to make it so those errors don't happen? If you need me to list the errors, tell me. Thanks

Yeah, some errors would help! (Not that I've ever tried to make a module.)

- taubz

That code compiled fine for me. I'm guessing that you are trying to compile this with something like gcc -o module module.c. This won't work, because the program has no entry point. Use gcc -c module.c (to compile module.o) or perhaps someone will contribute information about building a DSO.

Or maybe you forgot to -I/usr/src/linux/include .

thanks for your help. never mind about the errors now; that's all taken care of. but it says that the kernel's version is wrong. how can i fix this--turn some checking off? the book said i have to compile my own kernel. what is that? thanks

The kernal is the main part of an OS. In Linux device drivers are moduals that are called by the kernal. You have to recompile the kernal to get it to use a new modual. You can get kernal sources here: http://www.kernel.org/ or if you have Debian you can apt-get the kernal source. Note that the newest version is usually not a stable release.

I can't resist:

kernel

module

/me thinks we need a Quickstart guide on spelling :)

That spelling made even me wince.

"You can get kernal sources here: http://www.kernel.org/"

How is it that you can have two different spellings in one sentence?

Perhaps his finger slipped.

His finger slipped everywhere outside the URL???
To code a module you'll need to implement some entry point that are not standard (like the well known 'main()'). I don't remember the exact symbols for now, i'll post it a bit later. You'll need to use some macros (i don't believe #define MODULE will be enougth).
But, why do you want to code a kernal modual ???

why? well, i'd like to get into writing device drivers, and the book that teaches this introduces them. maybe i don't know enough yet, but it's good to learn anyway...

quite good idea...
I will retake at home some data i have got on a CD (he lays in my office). I have quickly read some parts of the document and i'am sure that your coding style is quite good with a 2.2 kernal ( :) ) but obsolete with a 2.4, as the entry points init_module() and cleanup_module()... sorry but if am right, your book too :( ...

thank you