I had put out an updated BB xenomai kernel a few days ago, and I promptly managed to loose the build notes.
So I had to do it once more, and better documented this time: http://git.mah.priv.at/gitweb/linuxcnc-kernel.git/blob/c7422c10a84e122ebb561d98e750b043390fd527:/linuxcnc/README.beaglebone . If this confuses you: you are not alone. the whole point of the exercise was to upgrade it to the latest ipipe patch because the old kernel as distributed until about a week ago wouldnt run xeno-regression-test properly - this one now does; while I was at it I upgraded from the TI-specific branches it uses as well. I think it is pretty much รก jour as far as the contents of the TI arago repo goes. I am at loss to judge how that pertains to the various tribal branches (Koen Kooi, Robert Nelson, this repo: https://github.com/beagleboard/kernel etc) Bas - if you need anything specific I'd be happy to give you access to this repo so you can add to it - diversity in this space is a waste of time. Anyway, them binariez are here: http://static.mah.priv.at/public/beaglebone/linux-3.2.21-xenomai+.tar.gz http://static.mah.priv.at/public/beaglebone/linux-headers-3.2.21-xenomai+.tar.gz pull and iron the first one over /, the second one over /usr/src . (actually the need for kernel headers to build userland thread styles will be removed shortly, they are needed only for the deprecated xenomai-kernel flavor; its more for completeness than anything else). I also upgraded the Xenomai userland package to track xenomai master (the work over there is very much in flux and 'release mode'). It is not necessary to upgrade that repo on your install for linuxcnc; kernel and userland support are very well decoupled in Xenomai. Branch is here: http://git.mah.priv.at/gitweb/xenomai-linuxcnc.git/shortlog/refs/heads/linuxcnc-master There are no fixes to the DHCP lease problem during boot in this image, although I noted that on NFS mount, the rtc is now set to the timestamp of the _last_ mount without the fixrtc boot option (which is a kludge to start with but obviously was considered 'more correct' than 1-1-1970). --- the hopes for anything based on the existing 3.4 or 3.5 ipipe ARM patches coming forward for the BB are low because there's no usable base versions in the 3.3-3.5 range. But then I found the 3.2.21 version very stable, modulo the DHCP lease issue, and that will be fixed without a new kernel. - Michael ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
