All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai list <xenomai@xenomai.org>
Subject: Re: [Xenomai] Porting a library to Xenomai
Date: Tue, 15 Dec 2015 16:16:23 +0100	[thread overview]
Message-ID: <1972107.aCc7hAvxek@soho> (raw)
In-Reply-To: <20151211163114.GE24775@hermes.click-hack.org>

El Divendres, 11 de desembre de 2015, a les 17:31:14, Gilles Chanteperdrix va 
escriure:
[...]

> 
> The fact that wrapping may be a problem for large applications where
> you only want a small part of the application to use xenomai
> services is the reason why Xenomai 3.x gives you another choice: do
> not wrap xenomai services, but specify you want to use them with the
> __RT() macro.

 ... following this thread. There's a point that I'm still confused: the rtnet 
part.

Since 2.6.4, rtnet was another project, that installed its includes (rtnet.h 
and rtmac.h) in its own place. From 3.x rtnet is integrated.

Looking the rtnet.h file, there are declared some #define and some include 
protected by __KERNEL__

My question is:

Using the POSIX wrapper, all the socket functions are wrap. But, how does it 
affect the rtnet part of the code? 

I mean, if I have a rtnet device, what is the difference of manually change all 
the network functions with a -DRTNET protected Realtime versions functions or 
use the wrap?

I understand that if I open a device that it's not rtnet, I lose the Realtime, 
although I open the device with a POSIX wrapped function. That's correct?

Best regards,

Leopold

-- 
--
Linux User 152692     GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://xenomai.org/pipermail/xenomai/attachments/20151215/67bbf584/attachment.sig>

  reply	other threads:[~2015-12-15 15:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 12:44 [Xenomai] Porting a library to Xenomai Leopold Palomo-Avellaneda
2015-12-11 13:20 ` Gilles Chanteperdrix
2015-12-11 14:03   ` Leopold Palomo-Avellaneda
2015-12-11 14:09     ` Gilles Chanteperdrix
2015-12-11 15:33       ` Leopold Palomo-Avellaneda
2015-12-11 16:31         ` Gilles Chanteperdrix
2015-12-15 15:16           ` Leopold Palomo-Avellaneda [this message]
2015-12-15 15:46             ` Gilles Chanteperdrix
2015-12-16 15:45               ` Leopold Palomo-Avellaneda
2015-12-17  0:05                 ` Gilles Chanteperdrix
2015-12-17  9:00                   ` Leopold Palomo-Avellaneda
2015-12-17  9:25                     ` Gilles Chanteperdrix

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=1972107.aCc7hAvxek@soho \
    --to=leo@alaxarxa.net \
    --cc=gilles.chanteperdrix@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.