There are two ways to build a *.ko file for a specific kernel version. New module can be added directly to a kernel source tree, or it can be build outside it. There are pros and cons of both scenarios, so and deciding on a way to go is a matter of personal favour.

Building a module outside a kernel tree is straightforward- all it takes is to use a makefile like the one attached to this text. By editing content of the configuration section shown below you can alter:

• path to the kernel sources that you'd like to finally insert your module to

It's been fifth time I do it in the last month, so here goes a little extract of what I've learned lately. This tutorial is gonna show you how to install the latest version of eclipse under Ubuntu- not the one available from the repository via apt-get utility, as it is often outdated, which I don't like. If you're ok with not using the latest version available- just install it with synaptic or apt-get.

• Download appropriate tar.gz from http://www.eclipse.org/downloads/ of whatever shape and flavour you like (I am using C/C++)

When working with linux kernel, powerful editor with symbols referencing is a must. As I am an Eclipse fan, I spent a lot of time trying to force it to cooperate with kernel. After some struggling I had found a great tutorial, that helped me a lot: http://simonkagstrom.livejournal.com/31079.html. Simon Kågström did a great job there (especially with the perl script), however there are few things I would do other way, e.g. I would not setup a project in kernel's directory, as it makes it even more messy.
So here is "my way" of making Eclipse and kernel come together.

Kernel image, which is built for IGEP during bitbake, is by default configured to not support Bright/Belkin USB Keyboard (1241:1503). If support for this device is needed, one has to rebuild kernel with .config file different than default one.

This is my sandbox, so please do not refer to content of this page and it's subpages, as their's content may be missleading or erroneous. Use it at your own risk!