Re: Qt application on Xenomai

Hi Henning, Thanks for your confirmation. Just to understand your set up further, does the POSIX layer used by QT is of the Xenomai skin ? Is This the way Qt is leveraging the rt features ? I guess the rendering of graphics is handled through non rt Linux framebuffer /opengl apis. Let me know

net.h missing in 3.0.8 tarball release

i got tarball of 3.0.8 from this linkhttps://xenomai.org/downloads/xenomai/stable/xenomai-3.0.8.tar.bz2In this file, there is no 'net.h' in 'xenomai-3.0.8/include/cobalt/kernel/rtdm/'It makes some error when i build kernel.i checked 'include/rtdm/net.h'. but this is different from original

Re: Re: Qt application on Xenomai

Hi, Henning: Just be curious, how did you run an c++/Qt applications in the RT domain on xenomai？ I am now runing the QT in non-rt domain, and may migrate it to the RT domain someday. -- -- Quan THANKS & BR! > >Message: 7 >Date: Fri, 1

Re: kvm fpu warning on 4.14.89

On 01.03.19 15:21, cagnulein wrote: Hi, with the last git the warning disappear, thanks. Now I would like to submit a new issue : with the last git and with the 4.14.89 also, if I run latency-test without the kvm guest on, everything works fine. If I run latency-test with the kvm guest on the

Re: kvm fpu warning on 4.14.89

Hi, with the last git the warning disappear, thanks. Now I would like to submit a new issue : with the last git and with the 4.14.89 also, if I run latency-test without the kvm guest on, everything works fine. If I run latency-test with the kvm guest on the system hangs! The entire system not only

Re: Qt application on Xenomai

Hi, i am not sure i fully understand the question. In case you are worried about combining Xenomai and Qt, i can assure you that it is possible. We do have big c++/Qt applications running both rt and non-rt on xenomai. regards, Henning Am Fri, 1 Mar 2019 14:10:42 +0530 schrieb Sumitabh Ghosh

[PATCH 4/4] Revert "clocksource: omap/dmtimer: ipipe: add support for user-visible TSC"

From: Jan Kiszka This reverts commit d35c49508ea205e86de96b005021f46d4199a861. Belongs into the ARM tree. Signed-off-by: Jan Kiszka --- arch/arm/plat-omap/dmtimer.c | 17 ++--- arch/arm/plat-omap/include/plat/dmtimer.h | 6 -- 2 files changed, 2 insertions(+),

[PATCH 2/4] Revert "clocksource: imx/imx53: ipipe: add support for user-visible TSC"

From: Jan Kiszka This reverts commit de53c9b26caa1c28785bb642350c07cfac6ebc3a. Belongs into the ARM tree. Signed-off-by: Jan Kiszka --- arch/arm/mach-imx/mach-imx53.c | 5 - 1 file changed, 5 deletions(-) diff --git a/arch/arm/mach-imx/mach-imx53.c b/arch/arm/mach-imx/mach-imx53.c index

[PATCH 1/4] ipipe: Revert changes to ARM arch_timer_set_cntkctl

From: Jan Kiszka This belongs into the ARM tree. Signed-off-by: Jan Kiszka --- arch/arm/include/asm/arch_timer.h | 4 1 file changed, 4 deletions(-) diff --git a/arch/arm/include/asm/arch_timer.h b/arch/arm/include/asm/arch_timer.h index e9e7656bc137..9327e3a101dc 100644 ---

[PATCH 0/4] ipipe-noarch: Revert arch/arm targeting commits

This commits should be present in the ARM tree only, the small change to arch_timer_set_cntkctl also in ARM64. By removing them from noarch, x86 will no longer touch any arch-alien folders. Jan Jan Kiszka (4): ipipe: Revert changes to ARM arch_timer_set_cntkctl Revert "clocksource:

[PATCH] ARM/ARM64: ipipe: Enable access to arch timer from user-space

From: Jan Kiszka This allows to expose the timer as clocksource directly to user-space by memory-mapping its registers. Signed-off-by: Jan Kiszka --- To be applied when splitting b597d0dec360 or after importing the partial revert of it from noarch. arch/arm/include/asm/arch_timer.h | 4

[PATCH 3/4] Revert "clocksource: imx/imx51: ipipe: add support for user-visible TSC"

From: Jan Kiszka This reverts commit 2f8ff661dfbfa84b14571d1629f73455b2bd707b. Belongs into the ARM tree. Signed-off-by: Jan Kiszka --- arch/arm/mach-imx/mach-imx51.c | 5 - 1 file changed, 5 deletions(-) diff --git a/arch/arm/mach-imx/mach-imx51.c b/arch/arm/mach-imx/mach-imx51.c index

Re: kvm fpu warning on 4.14.89

Yes qemu on a xenomai kernel (host device). My guest is a windows 10 2019. I'm already compiling the last git. I will let you know. Thanks Il ven 1 mar 2019, 11:24 Jan Kiszka ha scritto: > On 01.03.19 10:35, cagnulein via Xenomai wrote: > > I’m testing the 4.14.89 ipipe (i was usually using

Re: kvm fpu warning on 4.14.89

On 01.03.19 10:35, cagnulein via Xenomai wrote: I’m testing the 4.14.89 ipipe (i was usually using 4.9.146) and i’ve got a deterministic warning every time i start qemu. Is it already known? Thanks for reporting. I suppose this wasn't tested in a while. Just to be sure: You are starting

kvm fpu warning on 4.14.89

I’m testing the 4.14.89 ipipe (i was usually using 4.9.146) and i’ve got a deterministic warning every time i start qemu. Is it already known? Thanks R. Mar 1 01:14:05 debiankvm kernel: [ 96.078798] WARNING: CPU: 0 PID: 1154 at ./arch/x86/include/asm/fpu/internal.h:617

Re: kernel compile problem

On 01.03.19 07:46, C Smith via Xenomai wrote: I am unable to compile a xenomai-patched kernel. I get this message: warning: (XENOMAI) selects IPIPE which has unmet direct dependencies (HAVE_IPIPE_SUPPORT) kernel sources from kernel.org: 4.14.89 with ipipe-core-4.14.89-x86-2.patch applied gcc

Qt application on Xenomai

Hi, I have a generic question not specific to any platform. If I want to run a small graphics application on Xenomai 3.x what would be the correct approach. e.g. Qt application framework which needs POSIX apis and a linux frame buffer to be able to render 2D applications. Kindly provide me some

Re: Periodic timing varies across boots

On 3/1/19 9:05 AM, Philippe Gerum via Xenomai wrote: In order to mitigate this issue, you could try to isolate the > CPU used by the rt work loop using isolcpus, even if this can't block > any non-rt activity on that CPU, should read as: even if this can't fully block all non-rt activity on this

Re: Periodic timing varies across boots

On 3/1/19 8:30 AM, C Smith wrote: > On Wed, Feb 27, 2019 at 11:30 PM Philippe Gerum > wrote: > > On 2/28/19 6:56 AM, C Smith via Xenomai wrote: > > On Mon, Feb 25, 2019 at 12:09 AM Jan Kiszka > mailto:jan.kis...@siemens.com>> wrote: > > > >> On