Re: Regarding Xenomai patch installation on Live USB

Dear Fino, After doing all of the steps mentioned in the following link, https://github.com/intel/linux-stable-xenomai/wiki/Guide- the following error I am getting during testing on my C246P chipset based industrial motherboard loaded with Ubuntu18.04. $ sudo /opt/xenomai-3.1/bin/latency

[PATCH] Avoid a possible too early interrupt from the omap mcSPI controller

In order to avoid a possible too early interrupt from the omap mcSPI controller, disable interrupts before writing the number of bytes from the SPI message that fill up the omap mcSPI controller queue, and enable interrupts after that. Signed-off-by: Laurentiu-Cristian Duca ---

Re: [PATCH] testsuite/smokey: Do not load .gdbinit in gdb test

On 23.04.20 08:45, Vitaly Chikunov wrote: Avoid possible prompt being redefined in `.gdbinit' which could break gdb test. Signed-off-by: Vitaly Chikunov --- testsuite/smokey/gdb/gdb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git testsuite/smokey/gdb/gdb.c

RE: Regarding Xenomai patch installation on Live USB

>From: gopi ratnakaram Sent: Friday, April >24, 2020 3:44 PM > >Dear Fino, > >After doing all of the steps mentioned in the following link, >https://github.com/intel/linux-stable-xenomai/wiki/Guide- >the following error I am getting during testing on my C246P chipset based >industrial

Re: [PATCH] Avoid a possible too early interrupt from the omap mcSPI controller

On 24.04.20 13:41, Laurentiu-Cristian Duca via Xenomai wrote: In order to avoid a possible too early interrupt from the omap mcSPI controller, disable interrupts before writing the number of bytes from the SPI message that fill up the omap mcSPI controller queue, and enable interrupts after

Fwd: [PATCH] Avoid a possible too early interrupt from the omap mcSPI controller

-- Forwarded message - From: Laurentiu-Cristian Duca Date: Fri, Apr 24, 2020, 20:38 Subject: Re: [PATCH] Avoid a possible too early interrupt from the omap mcSPI controller To: Jan Kiszka In Xenomai the issue did not happen in my tests. It happened in the preempt_rt port of the

Re: [I-PIPE] ipipe-core-4.19.115-arm64-5 released

On 24.04.20 20:28, Greg Gallagher wrote: On Fri, Apr 24, 2020 at 2:06 PM Greg Gallagher > wrote: Sure no problem On Fri, Apr 24, 2020 at 2:00 PM Jan Kiszka mailto:jan.kis...@siemens.com>> wrote: On 22.04.20 06:34, xenomai--- via Xenomai wrote:

Re: [I-PIPE] ipipe-core-4.19.115-arm64-5 released

Sure no problem On Fri, Apr 24, 2020 at 2:00 PM Jan Kiszka wrote: > On 22.04.20 06:34, xenomai--- via Xenomai wrote: > > Download URL: > https://xenomai.org/downloads/ipipe/v4.x/arm64/ipipe-core-4.19.115-arm64-5.patch > > > > Repository: https://git.xenomai.org/ipipe-arm64 > > Release tag:

Re: [I-PIPE] ipipe-core-4.19.115-arm64-5 released

On Fri, Apr 24, 2020 at 2:06 PM Greg Gallagher wrote: > Sure no problem > > On Fri, Apr 24, 2020 at 2:00 PM Jan Kiszka wrote: > >> On 22.04.20 06:34, xenomai--- via Xenomai wrote: >> > Download URL: >> https://xenomai.org/downloads/ipipe/v4.x/arm64/ipipe-core-4.19.115-arm64-5.patch >> > >> >

Re: [I-PIPE] ipipe-core-4.19.115-arm64-5 released

On 22.04.20 06:34, xenomai--- via Xenomai wrote: Download URL: https://xenomai.org/downloads/ipipe/v4.x/arm64/ipipe-core-4.19.115-arm64-5.patch Repository: https://git.xenomai.org/ipipe-arm64 Release tag: ipipe-core-4.19.115-arm64-5 I think we have a build regression here:

Re: [I-PIPE] ipipe-core-4.19.115-arm64-5 released

On Fri, Apr 24, 2020 at 3:14 PM Jan Kiszka wrote: > > On 24.04.20 20:28, Greg Gallagher wrote: > > > > > > On Fri, Apr 24, 2020 at 2:06 PM Greg Gallagher > > wrote: > > > > Sure no problem > > > > On Fri, Apr 24, 2020 at 2:00 PM Jan Kiszka >

[I-PIPE] ipipe-core-4.19.115-arm64-6 released

Download URL: https://xenomai.org/downloads/ipipe/v4.x/arm64/ipipe-core-4.19.115-arm64-6.patch Repository: https://git.xenomai.org/ipipe-arm64 Release tag: ipipe-core-4.19.115-arm64-6