All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Jim Cromie <jim.cromie@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: Test, benchmark, demo frameworks
Date: Wed, 16 Aug 2006 09:12:07 +0200	[thread overview]
Message-ID: <44E2C547.30601@domain.hid> (raw)
In-Reply-To: <44DD08A0.5000603@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]

Jim Cromie wrote:
> Jan Kiszka wrote:
>> ...
>> So, how to proceed?
>>   
> <aside> wiki++ </>
> 
> 1 file at a time - I suppose..
> 
> I'll start by poaching Hannes' Makefile, bundling it into an examples/
> dir with
> my 3-way version of his timer programs.  Id like see the target files
> appear as 0 len files,
> ( presuming this necessary for svn diff to see code I drop in )
> 
> Then we can discuss the more nuanced improvements /* adding tutorial,
> guidance */
> 
> After that, its just step and repeat, tossing crap along the way.
> 

Ok, to ease pushing things into folders, I would suggest creating this
structure in the root dir of trunk:

examples/native/...
examples/native/kernel/...
examples/posix/...
examples/...
examples/drivers/can/...
examples/drivers/serial/...

All stuff self-contained, i.e. one should simply cd to the folder type
make, maybe additionally providing some information on the xenomai
installation dir / kernel source path, and some binary pops up, ready to
run or insmod.

I would furthermore suggest to have some kind of hello-xenomai.c in
every skin example folder that is intended as the beginners tutorial,
providing an elementary framework to start hacking.


Reorganising the testsuites is another topic. I currently have no idea
how to sort things. We have some stuff under sim/skins/*/testsuite that
only builds for the simulator, there is src/testsuite, intended to be
distributed and installed on the target, and we may want to have a
larger testsuite that can be downloaded separately (my concern is also
about driver tests here). Anyone any ideas/comments on this?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]

  reply	other threads:[~2006-08-16  7:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  1:18 [Xenomai-help] expected output and runtime of switchtest ? Jim Cromie
2006-08-10 11:28 ` Jan Kiszka
2006-08-10 20:38   ` [Xenomai-core] " Jim Cromie
2006-08-11 16:25     ` [Xenomai-core] Test, benchmark, demo frameworks (was: expected output and runtime of switchtest ?) Jan Kiszka
2006-08-11 22:45       ` [Xenomai-core] Re: Test, benchmark, demo frameworks Jim Cromie
2006-08-16  7:12         ` Jan Kiszka [this message]
2006-08-18 16:54       ` [Xenomai-core] Re: Test, benchmark Jim Cromie
2006-08-18 17:19         ` Gilles Chanteperdrix
2006-08-18 17:48           ` Gilles Chanteperdrix
2006-08-18 18:12           ` Jim Cromie
2006-08-18 18:23             ` Jan Kiszka
2006-08-18 19:10             ` Gilles Chanteperdrix
2006-08-18 21:28             ` Gilles Chanteperdrix
2006-08-18 18:02         ` Jan Kiszka
2006-08-18 18:28           ` Jim Cromie
2006-08-19  7:35             ` Jan Kiszka
2006-08-19 12:48               ` Gilles Chanteperdrix
2006-08-13 17:11     ` [Xenomai-core] expected output and runtime of switchtest ? 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=44E2C547.30601@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=jim.cromie@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.