[Xenomai] rtnet in Xenomai 3.0

[Xenomai] rtnet in Xenomai 3.0

[Jonas Platte]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

as the title suggests, I am trying to set up rtnet with Xenomai 3.0.

I already partly got rtnet to work with Xenomai 2.6 on a debian
machine with linux 3.4; I will try to get a linux 3.14.x or 3.16
kernel running there tomorrow [when I am at work again], because
cobalt requires at least 3.10 and the rtnet stuff wasn't installed
when I built Xenomai 3.0 for the 3.4 kernel with the mercury core so I
assumed for the moment that mercury core + rtnet isn't supported.

On my arch linux system at home I already tried the same thing though,
where installing a new kernel was simpler, but I wasn't successful.
Apparently, the rtnet tools (the programs rtnet, rtcfg, rtping and so
on) were installed but the kernel modules didn't even get built.

So I have two main questions:

* Is it true that rtnet is only available for the cobalt core?
  [I like to think that it isn't, and if I'm right about that
  I'd be happy to help fixing it. I have a fair amount of experience
  with the GNU build system / autotools.]
* How to build the rtnet kernel module and the rt_* ethernet drivers?
  I feel like I am missing a "make modules" (and "make modules_install")
  somewhere, but I only found automake-generated Makefiles that didn't
  have these targets and the Makefiles in kernel/, which look like they
  should be part of a recursive make call, but I didn't find that
  directory referenced anywhere but in EXTRA_DIST.

Also, a small thing that I might write dedicated email for if whoever
reads until here tells me that would be a good idea to make the right
people notice it:

I'm writing a C++11 (downwards compatibility currently not planned)
wrapper for the Xenomai / rtnet RTDM API. It will be released under
LGPL v3, unless xeno-- project is not as dead as it seems or someone
is willing to revive it (in which case I would love to integrate this
functionality there instead of making it a seperate library); or
someone gives me a good reason to release it under a different license.

Thanks to everyone who worked on porting rtnet to Xenomai 3.0 and
integrating it into the repository!

P.S.: The next email(s) from me will probably not come from this email
address, but from jonas.platte@iwes.fraunhofer.de. In case you want to
contact me directly, please use that address.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJU/T23AAoJEChniccSSv3r3akH/0IM+MxE5YKOk3SR1SWYVaD6
nwA+VsVGtOOGiP7QdvRaYiBnLw/7FcYX7mBO8/7ATe9Ke+0Z4evCu+EKv5guIQKy
jkAFZABNwO55lihPXhAgFRHK+KwfSMkKGSNAPbKsx8rwDDG2wkWdsamBCWOpmMQC
CM0Uq2ldchp66y58Wu5+Y9D37WsB8xopnX7AytrsKw/5lNcG3yvziRtRy5n3ox1d
If9fFUoIpfY+X5tAOkRk2fu9SZgvS/Yq6vRVgoy83cE3hoaQQsZAMvvZUH0mYu6z
DcPC0ZPafrYg5+ZyuNowM3kp7qpmGRnCaIHMSMP7zj74Z0oHh/MJSdxuEwToZvM=
=Y6kO
-----END PGP SIGNATURE-----

Re: [Xenomai] rtnet in Xenomai 3.0

[Gilles Chanteperdrix]

On Mon, Mar 09, 2015 at 07:29:11AM +0100, Jonas Platte wrote:
> Hi,

Hi Jonas,

> 
> as the title suggests, I am trying to set up rtnet with Xenomai 3.0.
> 
> I already partly got rtnet to work with Xenomai 2.6 on a debian
> machine with linux 3.4; I will try to get a linux 3.14.x or 3.16
> kernel running there tomorrow [when I am at work again], because
> cobalt requires at least 3.10 and the rtnet stuff wasn't installed
> when I built Xenomai 3.0 for the 3.4 kernel with the mercury core so I
> assumed for the moment that mercury core + rtnet isn't supported.
> 
> On my arch linux system at home I already tried the same thing though,
> where installing a new kernel was simpler, but I wasn't successful.
> Apparently, the rtnet tools (the programs rtnet, rtcfg, rtping and so
> on) were installed but the kernel modules didn't even get built.
> 
> So I have two main questions:
> 
> * Is it true that rtnet is only available for the cobalt core?
>   [I like to think that it isn't, and if I'm right about that
>   I'd be happy to help fixing it. I have a fair amount of experience
>   with the GNU build system / autotools.]

rtnet currently exists over cobalt only. It is planned to have RTnet
over mercury by first porting RTDM over native Linux, and in fact a
partial port of RTDM over native Linux exists, but the pieces have
not been tested together.


> * How to build the rtnet kernel module and the rt_* ethernet drivers?
>   I feel like I am missing a "make modules" (and "make modules_install")
>   somewhere, but I only found automake-generated Makefiles that didn't
>   have these targets and the Makefiles in kernel/, which look like they
>   should be part of a recursive make call, but I didn't find that
>   directory referenced anywhere but in EXTRA_DIST.

Rtnet has been integrated into Xenomai kernel-space support, so you
configure RTnet like xenomai kernel support: using the kernel
configuration menu. You will find RTnet configuration under the sub-menus

Xenomai/cobalt
Drivers
RTnet

Note that even though RTnet modules can be selected as built-in, they
currently only work when built as modules.

> 
> Also, a small thing that I might write dedicated email for if whoever
> reads until here tells me that would be a good idea to make the right
> people notice it:
> 
> I'm writing a C++11 (downwards compatibility currently not planned)
> wrapper for the Xenomai / rtnet RTDM API. It will be released under
> LGPL v3, unless xeno-- project is not as dead as it seems or someone
> is willing to revive it (in which case I would love to integrate this
> functionality there instead of making it a seperate library); or
> someone gives me a good reason to release it under a different license.

Can not answer about that.

> 
> Thanks to everyone who worked on porting rtnet to Xenomai 3.0 and
> integrating it into the repository!
> 
> P.S.: The next email(s) from me will probably not come from this email
> address, but from jonas.platte@iwes.fraunhofer.de. In case you want to
> contact me directly, please use that address.

Please note that the xenomai mailing list is subscriber only, so you
will need to subscribe with that second mail address to be able to
post.

Regards.

-- 
					    Gilles.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 811 bytes
Desc: not available
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20150309/eecaca41/attachment.sig>