All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ravid Baruch Naali <ravidbn@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Newbies developer instructions
Date: Wed, 29 Aug 2007 12:29:05 +0300	[thread overview]
Message-ID: <46D53C61.3060203@domain.hid> (raw)
In-Reply-To: <46D530AB.5080306@domain.hid>

Thanks Jan,


I'm working on an academic course which I will teach next semester on
Real Time system, in which I will bring both VxWorks and Xenomai as Hard
RT systems as an example.

Therefore it will be only natural for me to work on porting some
examples to VxWorks skin at first.

My plan is to implement the same operation in few methods:

- Using VxWorks skin

- Creating a driver (RTDM)

- Using POSIX API

Then document the Functions flow from the skin/RTDM calls down to the HAL.


Nevertheless,

_*Paul*_,  If I can assist you with the Xenomai LiveCD please contact me
and I will be happy to help.


As for the test suite I plan to give it as a project to one of my
students (What do you think?).


As soon as I'll fill


Jan Kiszka wrote:

> Ravid Baruch Naali wrote:
>   
>> Hello Xenomai-core mailing list,
>>
>>
>> I'm eager to contribute to the Xenomai project, but since I could not
>> find any opened bugs or a detailed task list apart from:
>>
>> http://www.xenomai.org/index.php/TaskMarket
>>
>> I was wondering if there is way for newbies like me to get involved?
>>
>> If any of you can send me a pointer to where should i begin, I will be
>> more then greatful.
>>     
>
> Über-cool - someone looking for work! :)
>
> There are a thousand things to do. The most productive things are likely
> those you stumble over when using Xenomai in your project. What is not
> working? What could be solved better or should be added? Also: What
> features should be checked against regressions while the development
> advances (more automatic test cases - very important!)?
>
> Besides this, here are some more potential points to start with:
>
>  o https://mail.gna.org/public/xenomai-core/2007-08/msg00017.html :)
>
>  o Write more examples/tutorials for your favourite skin (see examples
>    repos in SVN).
>
>  o Check the code against its (doxygen) documentation - everything still
>    up-to-date? Something yet undocumented?
>
>  o Work with Paul Corner (paul_c@domain.hid) on some regularly updated
>    Xenomai LiveCD (I guess he would be happy about help).
>
>  o Enhance the testsuite / test script to collect more data, and
>    specifically to evaluate the data more systematically (up to
>    re-creating something like http://issaris.org/rtai/summary.php). To
>    start with: I once had the idea to create some statistics collection
>    library for the testsuite so that all tests could use the same
>    infrastructure to process/visualise benchmark results.
>
>  o ... (things I forgot)
>
> Jan
>
>   


-- 
Ravid Baruch Naali
ravidbn@domain.hid
+972 4 6732729
+972 52 5830021



  reply	other threads:[~2007-08-29  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29  7:37 [Xenomai-core] Newbies developer instructions Ravid Baruch Naali
2007-08-29  8:39 ` Jan Kiszka
2007-08-29  9:29   ` Ravid Baruch Naali [this message]
2007-08-29 11:06     ` Jan Kiszka

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=46D53C61.3060203@domain.hid \
    --to=ravidbn@domain.hid \
    --cc=jan.kiszka@domain.hid \
    --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.