From: Philippe Gerum <rpm@xenomai.org>
To: Fillod Stephane <stephane.fillod@domain.hid>
Cc: rtai@domain.hid, adeos-main@gna.org
Subject: Re: [Adeos-main] RE: RTAI/fusion 0.7
Date: Thu, 31 Mar 2005 09:06:50 +0200 [thread overview]
Message-ID: <424BA18A.4060907@domain.hid> (raw)
In-Reply-To: <1CFEB358338412458B21FAA0D78FE86D505935@domain.hid>
Hi Stéphane,
Fillod Stephane wrote:
> Hi Philippe,
>
> Kudos for the RTAI/fusion 0.7 release!
> You (the team) are doing an astounding work.
Thanks.
>
> [snip]
>
>>o The Adeos support used in fusion has been upgraded to final releases,
>
>
>>namely r9/x86 and r6/ppc. Upgrading is strongly recommended, especially
>
>
>>if CONFIG_PREEMPT is enabled in your kernel config, which is likely
>
> with
>
>>fusion. Also note that Adeos PPC is now rebased on mainline (2.6.10
>>actually).
>
>
> Please find attached a patch of Adeos r6/ppc against 2.6.11.
> I hope I've got it right.
Looks so. Looking at the problem Heikki pointed us at, it would somewhat
affect 2.6.11 usability in RTAI/fusion context, since we would need to
run with CONFIG_PREEMPT disabled. No problem for RT stuff in primary
mode, but rather hopeless for using the secondary one efficiently.
Either we include Paul Mackerras's fix for it in the Adeos patch, or we
go directly for 2.6.12-rc, using your patch as a reference.
> Please let me know if it would need
> the spinlock fix in i386-r10c1.
>
It would be better, yes. This generic bug breaks deemed non-preemptible
sections in printk() at least. I've committed the changes to the Adeos
CVS (adeos-core/include/asm-ppc/adeos.h).
> Hope to get some Fusion report to share soon.
>
Ack. Thanks for the patch.
--
Philippe.
prev parent reply other threads:[~2005-03-31 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 16:56 [Adeos-main] RE: RTAI/fusion 0.7 Fillod Stephane
2005-03-30 18:12 ` Heikki Lindholm
2005-03-31 7:06 ` Philippe Gerum [this message]
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=424BA18A.4060907@domain.hid \
--to=rpm@xenomai.org \
--cc=adeos-main@gna.org \
--cc=rtai@domain.hid \
--cc=stephane.fillod@domain.hid \
/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.