From: Li Hongyu <lihongyu1999@bupt.edu.cn>
To: xenomai <xenomai@lists.linux.dev>
Cc: Philippe Gerum <rpm@xenomai.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Chen Hongzhan <hongzhan.chen@intel.com>,
Wang Rick Y <rick.y.wang@intel.com>, MengweiXu <mwx@bupt.edu.cn>,
Jorge Ramirez <jorge.ramirez.ortiz@gmail.com>,
Andrew Noren <andrew.noren@gmail.com>
Subject: [RROS] Introduce a rust dual-kernel RROS based on the dovetail
Date: Tue, 12 Dec 2023 07:16:26 +0000 [thread overview]
Message-ID: <EE82543C18AFC423+20231212071625.GA955@3cfae85af25a> (raw)
Hello,
At our recent meetup in Wuxi, China, we had the opportunity to discuss
the motivation behind and the current progress of RROS. Following the
successful launch of our satellite into space[1], we are excited to announce
the official open-sourcing of RROS, which is now available at
https://github.com/BUPT-OS/RROS](https://github.com/BUPT-OS/RROS
. For those interested in exploring RROS, you can find the code in the
kernel/rros directory on this repository.
We are thrilled to introduce RROS to the public. As mentioned in our earlier
presentation, our goal is to ensure compatibility with the libevl interface
and to strive for performance on par with EVL.
At present, we are still working towards full support for all interfaces of
libevl r27. Performance evaluations will commence once we have implemented
all the necessary features. We want to present our progress to the community
and discuss potential collaborations with the Xenomai/EVL community.
We look forward to your feedback and suggestions!
[1] https://bupt-os.github.io/website/news/2023_12_9/satellite_launch/
Best regards,
Hongyu Li
reply other threads:[~2023-12-12 7:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=EE82543C18AFC423+20231212071625.GA955@3cfae85af25a \
--to=lihongyu1999@bupt.edu.cn \
--cc=andrew.noren@gmail.com \
--cc=hongzhan.chen@intel.com \
--cc=jan.kiszka@siemens.com \
--cc=jorge.ramirez.ortiz@gmail.com \
--cc=mwx@bupt.edu.cn \
--cc=rick.y.wang@intel.com \
--cc=rpm@xenomai.org \
--cc=xenomai@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).