On 19.11.18 14:52, Henning Schild wrote:
Am Mon, 19 Nov 2018 10:52:34 +0100
schrieb Philippe Gerum :
On 11/19/18 10:40 AM, Henning Schild wrote:
Am Fri, 16 Nov 2018 07:23:47 +0100
schrieb Jan Kiszka :
On 09.11.18 10:14, Henning Schild via Xenomai wrote:
The test often asserted. This
Hi all,
just a quick note that I started a 4.4-cip based I-pipe tree:
https://gitlab.denx.de/Xenomai/ipipe/tree/ipipe-4.4.y-cip
So far it's just a merge of ipipe-4.4.y @ipipe-core-4.4.166-x86-12 with the CIP
tree @4.4.166-cip29. I'm not yet sure whether to switch 4.4 completely to -cip
or
> -Original Message-
> From: Jan Kiszka
> Sent: Donnerstag, 20. Dezember 2018 14:33
> To: Lange Norbert ; Xenomai
> (xenomai@xenomai.org)
> Subject: Re: Cobalt Preemption of kernel update_fast_timekeeper can cause
> deadlocks
>
> E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY MEASURE,
Download URL:
https://xenomai.org/downloads/ipipe/v4.x/x86/ipipe-core-4.4.166-x86-12.patch
Repository: https://git.xenomai.org/ipipe-x86
Release tag: ipipe-core-4.4.166-x86-12
On 20.12.18 13:29, Lange Norbert via Xenomai wrote:
On 19.12.18 19:26, Auel, Kendall via Xenomai wrote:
Jan,
I'm very much in favor of providing a way to prevent Xenomai modules
from using features which can result in deadlock, if there is a clean way to
detect such a situation.
We used
> On 19.12.18 19:26, Auel, Kendall via Xenomai wrote:
> > Jan,
> >
> > I'm very much in favor of providing a way to prevent Xenomai modules
> from using features which can result in deadlock, if there is a clean way to
> detect such a situation.
> >
> > We used gettimeofday in one of our modules
On 19.12.18 19:26, Auel, Kendall via Xenomai wrote:
Jan,
I'm very much in favor of providing a way to prevent Xenomai modules from using
features which can result in deadlock, if there is a clean way to detect such a
situation.
We used gettimeofday in one of our modules and it mostly worked
On 20.12.18 09:28, Mauro Salvini via Xenomai wrote:
Hi all,
I'm testing Xenomai 3 on an Intel Braswell board (Atom x5-E8000).
I'm using ipipe kernel at last commit from [1], branch ipipe-4.9.y,
64bit build on a Debian Stretch 9.6 64bit.
Xenomai library is from [2], branch stable/v3.0.x on
On 20.12.18 09:59, duanwujie wrote:
Hi, Phi and Jan:
The correct handler is handle_percpu_irq !
Hi, Phi and Jan:
I try to port the ipipe to mips arch according the
https://gitlab.denx.de/Xenomai/xenomai/wikis/Porting_Xenomai_To_A_New_Arm_SOC#terminology
Now it
Hi, Phi and Jan:
The correct handler is handle_percpu_irq !
Hi, Phi and Jan:
I try to port the ipipe to mips arch according the
https://gitlab.denx.de/Xenomai/xenomai/wikis/Porting_Xenomai_To_A_New_Arm_SOC#terminology
Now it worked on the single cpu,but SMP
Hi all,
I'm testing Xenomai 3 on an Intel Braswell board (Atom x5-E8000).
I'm using ipipe kernel at last commit from [1], branch ipipe-4.9.y,
64bit build on a Debian Stretch 9.6 64bit.
Xenomai library is from [2], branch stable/v3.0.x on commit bc53d03f (I
haven't two last commits but seems not
11 matches
Mail list logo
