From: Philippe Gerum <rpm@xenomai.org>
To: xenomai-core <xenomai@xenomai.org>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: [Xenomai-core] [RESEND] State of the Xenomai/ia64 port
Date: Tue, 27 Jan 2009 19:07:46 +0100 [thread overview]
Message-ID: <497F4D72.1020504@domain.hid> (raw)
In-Reply-To: <496F12DD.40500@domain.hid>
Last resend before removal of the ia64 support.
Philippe Gerum wrote:
> It has been 2.5 years since we saw an update to the Xenomai/ia64 port, and there
> is still no sign of life coming from ia64 users (do we actually have any
> Xenomai/ia64 users? maybe one, a single one?). To sum up the situation:
>
> - our ia64 port stalled in 2.6.16.
> - we had zero feedback from anyone regarding the Xenomai/ia64 port since it was
> introduced in 2005 (no, I won't buy the "there was no bug to report" explanation
> for this; it has been a while since Santa Claus told me he was a fake).
> - there is no incentive to rejuvenate the ia64 port on my side, given that I
> would definitely use PREEMPT_RT to gain real-time guarantees instead of a
> co-kernel on this particular architecture.
> - We did not hear of anyone having such incentive yet.
>
> Letting an architecture port bit rot in Xenomai is not an option, and
> maintaining a useless port makes no sense. 2.5 brings in a number of new
> features, and it is crucial that all of the Xenomai ports support them properly.
>
> If you think I'm badly wrong, utterly misinformed, or just nuts (whichever comes
> first), you may want to speak up now. 2.5-rc1 is due for the first week of
> February, and I plan to remove the ia64 support before our first release
> candidate is out, unless somebody convinces me that I should not do that.
>
--
Philippe.
prev parent reply other threads:[~2009-01-27 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 10:41 [Xenomai-core] State of the Xenomai/ia64 port Philippe Gerum
2009-01-27 18:07 ` 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=497F4D72.1020504@domain.hid \
--to=rpm@xenomai.org \
--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.