Hi all,

Thanks for the help so far on building an smp kernel. I think I understand
the basic process of building a kernel, selecting the features I want in the
kernel, and building a kernel with the rtai extensions. I am still a bit
lost however on the exact versions of kernel and rtai code to use, and the
repositories from which to get them.

The rtai kernel which installs with the hardy version of EMC is version
2.6.24-16-rtai. I was assuming that derives from some standard Linux kernel
like 2.6.24-16-generic. When booting the default kernel with Ubuntu hardy,
the current kernel version is 2.6.24-23-generic. My Debian Lenny install
uses kernel version 2.6.26-1-686.

Looking at the kernels available at kernel.org
(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/) those go up to 2.6.24.7 (not
"-"). I also see that Ubuntu seems to have its own kernels which are of the
form 2.6.24-n. I haven't searched the Debian site for what repositories of
kernels it may have.

Then looking at the rtai patches available under
/usr/src/modules/rtai/base/arch/x86_64/patches, I see the latest patch to
be:
hal-linux-2.6.23-x86_64-1.4-03.patch.

How was the current kernel 2.6.24-16-rtai generated when the latest rtai
patch is 2.6.23... What is the -magma kernel Mario was referring to?

Basically my question is, what is the latest usable kernel and rtai patch,
and where do I get them? What is the specific kernel version used to create
the current Hardy kernel for EMC? Which repository do I use to get the
kernel code, the kernel.org repositories, the Ubuntu repositories or the
Debian repositories?

Looks like my case of fools rush in where angels fear to tread. :)

Thanks,
Eric


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to