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 ch
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 ow
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
> corre
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.
--
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 pas
Yes, the measurements are on no-load scenarios.
I will try to repeat my measurements with system-loads as you suggest.
Following is the cpu-info of my board:
--
Processor : ARM926EJ-S rev 5 (v5l)
BogoMIPS: 131.48
Features
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:
> 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 fi
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 sheets.
- find out, how addi
On Thu, 2010-06-24 at 11:22 +0200, Tschaeche IT-Services wrote:
> On Sat, Jun 19, 2010 at 01:11:17AM +0200, Philippe Gerum wrote:
> > On Wed, 2010-06-09 at 20:11 +0200, Tschaeche IT-Services wrote:
> > > On Wed, Jun 09, 2010 at 12:41:23PM +0200, Philippe Gerum wrote:
> > > > We definitely need user
Tschaeche IT-Services wrote:
> On Sat, Jun 19, 2010 at 01:11:17AM +0200, Philippe Gerum wrote:
>> On Wed, 2010-06-09 at 20:11 +0200, Tschaeche IT-Services wrote:
>>> On Wed, Jun 09, 2010 at 12:41:23PM +0200, Philippe Gerum wrote:
We definitely need user feedback on this. Typically, does arming
11 matches
Mail list logo
