All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Nicolodi <daniele@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Xenomai 3 documentation
Date: Thu, 02 Feb 2012 19:22:30 +0100	[thread overview]
Message-ID: <4F2AD466.3070007@domain.hid> (raw)
In-Reply-To: <4F2ACF96.2080503@domain.hid>

On 02/02/12 19:01, Philippe Gerum wrote:
> On 02/02/2012 06:29 PM, Daniele Nicolodi wrote:
>> Hello,
>>
>> I'm looking with curiosity to the development of Xenomai 3 skimming
>> through the GIT commits. I'm a physicist writing data acquisition code,
>> looking at how experienced programmers solve problems is very
>> instructional. However, I have observed that most of the code that has
>> been added do not have documentation in the form of comment blocks.
>>
>> There is some other place where I can learn about Xenomai 3 ?
> 
> A general roadmap explaining high level issues:
> http://www.xenomai.org/index.php/Xenomai:Roadmap#Toward_Xenomai_3
> 
> For the rest, the Cobalt kernel is fully documented in the sources, 
> since it directly derives from v2.x's nucleus, check kernel/cobalt.
> 
> The really missing part is a documentation of the lib/copperplate API, 
> providing the building blocks for the userland-based RTOS skins. That 
> one is still wandering somewhere in my brain. But for sure, it will land 
> in the sources at some point as well.

Thank Philippe,

working mostly in user space, copperplate is the part I'm most
interested in. The code is self explanatory enough, but sometimes I fail
to see the big picture...

Cheers,
Daniele


      reply	other threads:[~2012-02-02 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 17:29 [Xenomai-help] Xenomai 3 documentation Daniele Nicolodi
2012-02-02 18:01 ` Philippe Gerum
2012-02-02 18:22   ` Daniele Nicolodi [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=4F2AD466.3070007@domain.hid \
    --to=daniele@domain.hid \
    --cc=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.