From: Jan Kiszka <jan.kiszka@domain.hid>
To: OB <obconseil@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Xenomai port on CRIS architecture
Date: Fri, 22 Sep 2006 08:40:13 +0200 [thread overview]
Message-ID: <4513854D.5050500@domain.hid> (raw)
In-Reply-To: <1158905195.24605.7.camel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
OB wrote:
> Hello,
>
> I could not find any reference to a port of Xenomai (Adeos) on the
> Etrax/CRIS architecture.
> There are reference to an RTAI port, without any activity at the moment.
Supporting an architecture is not "just" about writing a patch once, it
is also takes someone to keep an eye on it so that it evolves with the
projects, Linux kernel and RT-extension. The absolute minimum
requirement are active users/testers reporting any brokenness, even
better a maintainer providing fixes/updates. Obviously, this didn't work
for the RTAI port.
>
> If nobody is working on it, I'm ok to try !
You are welcome!
>
> My reference plateform is a FOX board, which include several GPIO and
> even a parallel port-like interface.
> http://www.acmesystems.it/?id=4
>
> Also, please let me know if anybody has any interest in this projet
> (beside me!)
>
Maybe there are not already dozens of people waiting for CRIS support,
but once we have a clean and working port, I guess there will be people
showing up. Doing a bit advertising later in CRIS-related forums or to
board vendors can accelerate this even further.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-09-22 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 6:06 [Xenomai-core] Xenomai port on CRIS architecture OB
2006-09-22 6:40 ` Jan Kiszka [this message]
2006-09-23 0:33 ` Paul
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=4513854D.5050500@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=obconseil@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.