From: Jan Kiszka <jan.kiszka@domain.hid>
To: "Thomas, Brieuc (GE Healthcare)" <Brieuc.Thomas@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] PB to patch a 2.6.16 kernel with an adeos-ipipe-2.6.14-ppc
Date: Sun, 09 Jul 2006 19:20:09 +0200 [thread overview]
Message-ID: <44B13AC9.3050307@domain.hid> (raw)
In-Reply-To: <5B122FD931231D408AC32630D1B1F7290C8BBB60@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
Thomas, Brieuc (GE Healthcare) wrote:
> Hi everybody !
>
> I've got a PPC-MPC8540 target with a 2.6.16 patch from the provider. I
> would like to patch my 2.6.16 kernel with an adeos-ipipe-2.6.14-ppc. Has
> somebody already done this?
> Up to now, I've done the patch manually and the compilation with
> xenomai-2.1.2...
Migrating some version steps upward in 2.6.x can be problematic. Also
the patches you got from the board vendor may collide with ipipe. What
conflicts did you have to resolve? Were you able to verify if those were
not related to relevant functional changes in the kernel?
> When I launch my target, the boot run without errors. But when I launch
> an Xenomai application (like latency) I've got a "kernel oops" message
> (during the task creation).
What does the oops precisely say, what's the backtrace about?
> can somebody help me to patch correctly my kernel?
Is your kernel patch publicly available? What parts does it touch
(critical for ipipe are IRQ and timer management).
Maybe someone from the PPC fraction on this list can comment on the
status of vanilla 2.6.16 vs. 2.6.14, also wrt ipipe/xenomai.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2006-07-09 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 13:55 [Xenomai-help] PB to patch a 2.6.16 kernel with an adeos-ipipe-2.6.14-ppc Thomas, Brieuc (GE Healthcare)
2006-07-09 17:20 ` Jan Kiszka [this message]
2006-07-09 17:32 ` Philippe Gerum
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=44B13AC9.3050307@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Brieuc.Thomas@domain.hid \
--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.