If your kernel configuration modifications happen to result in the generation of any loadable modules, then you will wind up with another file in the deployment images folder:

If your kernel configuration modifications happen to result in the generation of any loadable modules, then you will wind up with another file in the deployment images folder:

−

</pre>

+

<pre>

$ cd ${OETREE}/angstrom-dev/deploy/glibc/images/beagleboard

$ cd ${OETREE}/angstrom-dev/deploy/glibc/images/beagleboard

−

$ ls mod*

+

$ ls

</pre>

</pre>

Revision as of 20:08, 11 March 2010

There are several ways to get and configure the kernel. You could go to the [www.kernel.org The Linux Kernel Archives] find the ---arm--- branch, download a kernel and patch it for the omap. You could use git to get a kernel. Or you could just use bitbake like we did before.

Let's first learn how to do it the bitbake way. I'll also include some instructions for using git.

bitbake

When you did ECE597 Installing The Ångström Distribution you used bitbake to build console-image. During that build the kernel was downloaded and compiled. If you used the default configure, the source code was removed once it was done. Check and see:

cd ${OETREE}/angstrom-dev/work/beagleboard/angstrom-linux-gnueabi
ls

You should see a directory starting with linux-omap-. The rest of the name tells what version you have. Change to that directory and see what's there:

cd linux-omap-2.29-r46
ls

If you see a git directory, you are in luck. If you see just a temp directory you need to do the following to reload the sources:

cd ${OETREE}/build/conf
gedit local.conf

Find the line near the top that says INHERIT += " rm_work " and comment it out.