All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: "Wu, Aaron" <Aaron.Wu@analog.com>,
	"rtnet-developers@lists.sourceforge.net"
	<rtnet-developers@lists.sourceforge.net>,
	Xenomai <xenomai@xenomai.org>
Cc: "Zhang, Sonic" <Sonic.Zhang@analog.com>
Subject: Re: [Xenomai] status of rtnet
Date: Thu, 05 Mar 2015 11:45:09 +0100	[thread overview]
Message-ID: <54F833B5.3070408@web.de> (raw)
In-Reply-To: <649EF91064D35D40B9C93A225BF416746132B064@NWD2MBX7.ad.analog.com>

On 2015-03-05 09:17, Wu, Aaron wrote:
>> -----Original Message-----
>> From: Jan Kiszka [mailto:jan.kiszka@web.de]
>> Sent: 2015年3月5日 16:02
>> To: Wu, Aaron; rtnet-developers@lists.sourceforge.net; Xenomai
>> Subject: Re: status of rtnet
>>
>> On 2015-03-05 06:51, Wu, Aaron wrote:
>>> Hello,
>>>
>>> >From http://www.rtnet.org I saw the latest release of rtnet is years ago,
>> latest kernel support is 3.2. What's the status and roadmap of this project? Any
>> plan/schedule to support the newer version of kernel and xenomai?
>>
>> Fortunately, RTnet has been "adopted" by the Xenomai project (its list is on CC).
>> So the next RTnet release will actually be the next major Xenomai release: 3.0.
>> You can already pick up the latest 3.0-rc of Xenomai to obtain a more recent
>> version than what can be found in the RTnet git.
>>
>> Jan
>>
> 
> Thanks for the good news, in the latest 3.0-rc Xenomai code I saw there is support for kernel 3.16 for ARM, I would expect Rtnet works on 3.16 kernel for ARM too.

I would assume the same about the core as well. But you will have to
check if your target system's NIC is already supported or if some driver
porting is still required.

Jan


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20150305/11b4cc1d/attachment.sig>

  parent reply	other threads:[~2015-03-05 10:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <649EF91064D35D40B9C93A225BF416746132AF7E@NWD2MBX7.ad.analog.com>
2015-03-05  8:01 ` [Xenomai] status of rtnet Jan Kiszka
     [not found]   ` <649EF91064D35D40B9C93A225BF416746132B064@NWD2MBX7.ad.analog.com>
2015-03-05 10:45     ` Jan Kiszka [this message]
2015-03-05 12:30 Mariusz Janiak

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=54F833B5.3070408@web.de \
    --to=jan.kiszka@web.de \
    --cc=Aaron.Wu@analog.com \
    --cc=Sonic.Zhang@analog.com \
    --cc=rtnet-developers@lists.sourceforge.net \
    --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.