![]() The second seems to have been incorporated in v3.6 of the mainstream kernel. Is it possible to determine whether the installation is indeed realtime AFTER installing the kernel and booting BeagleBoard with it? Is there anything that I can check to verify that I have the kernel I want? Was there anything wrong with my config file or with my file copy procedure? If anybody made this work with BeagleBoard patches please explain. I was obviously using a cross compiler for the correct architecture, etc. I didn't see any links either so didn't change anything there. There was no zImage, only a vmlinuz file in the small, fat partition. I copied the zImage file to the boot directory in my ext4 partition to replace the old file. , git commit and git checkout -b Xenomai. I patched v3.2.21 using Xenomai supplied files. I saw a new Kernel configuration option for enabling Xenomai. I found that the last file to get patched, vmalloc.c was more likely to cause problems when kernel version was not an exact match. That is important because Robert's set of patches only works with git repos. I was able to apply the 3.2.21 patch to kernel release 3.2.21 which I had to get with wget. ![]() The Xenomai kernel appears to be extremely release-sensitive. ![]() I read the shell scripts provided by Robert, patched a certain release of the kernel and listened to Kroah-Hartman's video on kernel patching. I still don't have the Xenomai kernel but here is the progress I made so far. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |