[PATCH v2] boilerplate: Fix non-conforming usage of typeof in interface, headers

From: Jan Kiszka This fixes build breakages when using standard-conforming build, e.g. -std=c++11. Reported-by: Stéphane Ancelot Reported-by: Cris Almaraz Signed-off-by: Jan Kiszka --- This should make everyone happy. include/boilerplate/tunables.h | 4 ++-- 1 file changed, 2

[PATCH 2/2] alchemy/mutex: Fix typo in comment

s/rt_mutex_acquite/rt_mutex_acquire Signed-off-by: Richard Weinberger --- lib/alchemy/mutex.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/alchemy/mutex.c b/lib/alchemy/mutex.c index ffdc2dbea323..42cd1375b34b 100644 --- a/lib/alchemy/mutex.c +++ b/lib/alchemy/mutex.c

[PATCH 1/2] demo/alchemy/altency: Use sigdebug_reason()

Since cobalt adds 0xfccf to si_value we can no longer use the raw value. Signed-off-by: Richard Weinberger --- demo/alchemy/altency.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/demo/alchemy/altency.c b/demo/alchemy/altency.c index 83cc806b5d7f..4b49755edaba 100644

Re: [PATCH] boilerplate: Fix bogus "typeof(type)" in macros

On 10.07.19 22:50, Philippe Gerum wrote: > On 7/10/19 9:39 PM, Jan Kiszka via Xenomai wrote: >> From: Jan Kiszka >> >> This was ignored by most compilers so far, but it breaks at least under >> c++11. > > This was hardly ignored since this evaluates to a required type > information, the issue is

Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

as scrubbed... Name: 0001-ipipe-Activate-IRQ-in-ipipe_enable_irq.patch Type: text/x-patch Size: 1011 bytes Desc: not available URL: <http://xenomai.org/pipermail/xenomai/attachments/20190710/55e16f8f/attachment.bin> -- next part -- A non-text attachment was scrubbed... N

Re: [PATCH] boilerplate: Fix bogus "typeof(type)" in macros

On 7/10/19 9:39 PM, Jan Kiszka via Xenomai wrote: > From: Jan Kiszka > > This was ignored by most compilers so far, but it breaks at least under > c++11. This was hardly ignored since this evaluates to a required type information, the issue is rather with typeof() belonging to the GNU extension

AW: use of posix function clock_gettime

> First of all, all in-kernel APIs have been deprecated and removed in favor of > RTDM driver APIs. However, RTDM does not expose this clock directly. You can > only do rtdm_clock_read (realtime) or rtdm_clock_read_monotonic(). This was also my recognising after reading the code and the

[PATCH] boilerplate: Fix bogus "typeof(type)" in macros

From: Jan Kiszka This was ignored by most compilers so far, but it breaks at least under c++11. Reported-by: Stéphane Ancelot Reported-by: Cris Almaraz Signed-off-by: Jan Kiszka --- Thanks for reporting (and sorry for the long patch delay). This should fix it.

[Xenomai] c++11 issue

Hi all, I have a problem similar to the one described in https://xenomai.org/pipermail/xenomai/2018-February/038373.html. Compiling with -std=c++11 and adding the headers: #include #include Error extract: In file included from /usr/xenomai/include/xenomai/tunables.h:21:0,

RE: Best way to detect if a filedescriptor is a cobalt filedescriptor (/socket)

> -Original Message- > From: Jan Kiszka > Sent: Mittwoch, 10. Juli 2019 08:13 > To: Lange Norbert ; Xenomai > (xenomai@xenomai.org) ; Philippe Gerum > > Subject: Re: Best way to detect if a filedescriptor is a cobalt filedescriptor > (/socket) > > E-MAIL FROM A NON-ANDRITZ SOURCE: AS A

RE: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

> -Original Message- > From: Jan Kiszka > Sent: Dienstag, 9. Juli 2019 19:54 > To: Lange Norbert ; Xenomai > (xenomai@xenomai.org) ; Philippe Gerum > > Subject: Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up > > E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY

Re: Best way to detect if a filedescriptor is a cobalt filedescriptor (/socket)

On 09.07.19 16:49, Lange Norbert via Xenomai wrote: > Hi, > > I am opening a packetsocket, which is supposed to be realtime. Unfortunatly > if the rtpacket (rtnet?) module is not loaded, > then this will just silently fall back to a linux packet socket. Then later > demote thread during