From: Doug Brunner <dbrunner@ebus.com>
To: xenomai@xenomai.org
Subject: [Xenomai] Upgrading to Xenomai 2.6.1
Date: Thu, 30 Aug 2012 23:40:15 -0700 [thread overview]
Message-ID: <50405C4F.5030301@ebus.com> (raw)
I've been having a very hard time with the upgrade from Xenomai 2.6.0 to
2.6.1--hoping someone might have a suggestion for me. My thinking was
that, to get the most possible bug fixes, I should also upgrade to the
latest kernel for which there is a stable I-pipe patch, which appears to
be 3.2.21 from examining the list of available patches distributed with
Xenomai.
Unfortunately, 3.2.21 (even unmodified, using a vanilla Debian kernel
config, set for 586 cpu type) will not boot on my target platform
(Winsystems PPM-LX800-G, which has a Geode LX800 CPU). It immediately
resets after "Loading initial ramdisk", without even any early printk
output. I have no idea what could be causing that :(
I can't use CONFIG_MGEODE_LX because I get the following error building
with the I-pipe patch:
arch/x86/lib/mmx_32.c: In function '_mmx_memcpy':
arch/x86/lib/mmx_32.c:33: error: 'ipipe_root_domain_p' undeclared (first
use in this function)
arch/x86/lib/mmx_32.c:33: error: (Each undeclared identifier is reported
only once
arch/x86/lib/mmx_32.c:33: error: for each function it appears in.)
and including <linux/ipipe.h> in mmx_32.c does not help.
I did see an email on the list suggesting that 3.4 is now supported, but
if it is still in git and not released I'm guessing it hasn't undergone
much testing yet. For a production environment, would I be better off
just using 2.6.38.8?
I'd really like to get 2.6.1 running so I can see if it fixes the kernel
oops I reported a few months ago.
Thanks,
--
Doug Brunner
next reply other threads:[~2012-08-31 6:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 6:40 Doug Brunner [this message]
2012-08-31 7:13 ` [Xenomai] Upgrading to Xenomai 2.6.1 Gilles Chanteperdrix
2012-08-31 7:39 ` Gilles Chanteperdrix
2012-09-02 23:48 ` Doug Brunner
2012-09-03 5:28 ` Gilles Chanteperdrix
2012-09-04 7:27 ` Doug Brunner
2012-09-04 8:09 ` Gilles Chanteperdrix
2012-09-05 3:11 ` Doug Brunner
2012-09-05 7:05 ` Gilles Chanteperdrix
2012-09-04 8:53 ` Jim Cromie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50405C4F.5030301@ebus.com \
--to=dbrunner@ebus.com \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.