From: Jan Kiszka <jan.kiszka@domain.hid>
To: Miguel Angel Alvarez <ma.alvarez@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Newbie and Coldfire
Date: Mon, 24 Jul 2006 19:27:37 +0200 [thread overview]
Message-ID: <44C50309.70303@domain.hid> (raw)
In-Reply-To: <44C4E547.10304@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
Miguel Angel Alvarez wrote:
> Hi.
>
> I do not know if this in the correct mailing list to do this question.
> If not, please redirect me to the correct one.
>
> I am beginning a new proyect using a Coldifre micro (Have previous
> experience with i386 and PPC). It is also my first proyect with real
> time linux, so I have began to read articles about preemption patches,
> RTAI...
>
> It seems that Xenomai is the best effort to obtain hard real-time
> characteristics to my system, but... it is not ported to support
> Coldfire. Could anyone give me an advise on the difficulty of porting
> the systen to this architecture? Should I consider it just impossible?
>
Disclaimer: No expert on Coldfire speaking here. But given that Xenomai
already runs fine over Blackfin (also a MMU-less arch) and that it has a
clean architecture abstraction: should definitely be feasible.
The first step always involves an Adeos I-pipe patch. Check available
patches for other archs to assess the required effort for you. Feel free
to drop questions on their design or your Coldfire ideas on
xenomai-core/help or on adeos-main (similar people will listen).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-07-24 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 15:20 [Xenomai-help] Newbie and Coldfire Miguel Angel Alvarez
2006-07-24 17:27 ` Jan Kiszka [this message]
2006-07-26 7:39 ` Miguel Angel Alvarez
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=44C50309.70303@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=ma.alvarez@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.