Nero Fernandez wrote:
Thanks for your response, Philippe.
The concerns while the carrying out my experiments were to:
- compare xenomai co-kernel overheads (timer and context switch latencies)
in xenomai-space vs similar native-linux overheads. These are
presented in
the first two
Philippe Gerum wrote:
I've toyed a bit to find a generic approach for the nucleus to regain
complete control over a userland application running in a syscall-less
loop.
The original issue was about recovering gracefully from a runaway
situation detected by the nucleus watchdog, where a
Nero Fernandez wrote:
Yes, the measurements are on no-load scenarios.
I will try to repeat my measurements with system-loads as you suggest.
You can find a working root filesystem image with Xenomai 2.5.3 compiled
here:
http://www.xenomai.org/~gch/pub/rootfs-arm926-ejs.tar.bz2
The root
Nero Fernandez wrote:
As far as the adeos patch is concerned, i took a recent one (2.6.32) and
back-ported
it to 2.6.18, so as not to lose out on any new Adeos-only upgrades.
There is no such thing as an Adeos patch for linux 2.6.32 on the ARM
platforme.
--
Hi,
Alexis Berlemont wrote:
Hi Stefan,
Stefan Schaal wrote:
Hi Alexis,
I was just wondering whether the new experimental branch in your git
repository is something that can be tried already.
No. Not yet. This branch is aimed at temporarily holding the
corrections I am
Hi,
Alexis Berlemont wrote:
Hi,
Daniele Nicolodi wrote:
Alexis Berlemont wrote:
Daniele Nicolodi wrote:
After fixing analogy to permit continuous acquisition, I discovered that
ongoing commands are not canceled when a device is closed (I obtain a
DMA buffer owerwrite warning in
Hi,
I just pushed into my git repository (branch analogy) some significant
changes in the asynchronous buffer management.
These modifications intend to fix a major issue in the analogy
architecture: only the default input and output subdevices were
reachable via read / write syscalls.
These
