What are the differences among these similar nanosleep functions?

What are the differences among these similar nanosleep functions, especially the second one and the third one: https://gitlab.denx.de/Xenomai/xenomai/-/blob/v3.1/lib/cobalt/clock.c: line：353 COBALT_IMPL(int, nanosleep, (const struct timespec *rqtp, struct timespec *rmtp)) { int ret; ret =

Re: Receiving "Operation Not Permitted" when setting RTCAN_RTIOC_RCV_TIMEOUT and reading from CAN over cobalt pthread

From: Jan Kiszka Sent: Wednesday, July 1, 2020 9:43 PM To: Josh Karch ; xenomai@xenomai.org Subject: Re: Receiving "Operation Not Permitted" when setting RTCAN_RTIOC_RCV_TIMEOUT and reading from CAN over cobalt pthread On 01.07.20 16:55, Josh Karch via

Re: ARM: switchtest fails

On Thu., Jul. 2, 2020, 6:16 a.m. Jan Leupold via Xenomai < xenomai@xenomai.org> wrote: > Hi, > > I have a problem with switchtest, executed on sama5d2, > ipipe-4.19.128-cip28, xenomai-3.1. > > When started without arguments: > == Testing FPU check routines... > d0: 1 != 2 > ... snip ... > d15: 1

ARM: switchtest fails

Hi, I have a problem with switchtest, executed on sama5d2, ipipe-4.19.128-cip28, xenomai-3.1. When started without arguments: == Testing FPU check routines... d0: 1 != 2 ... snip ... d15: 1 != 2 == FPU check routines: OK. == Threads: sleeper_ufps-0 rtk-1 rtk-2 rtk_fp-3 rtk_fp-4 rtk_fp_ufpp-5

RTDM module ownership

Hi! I'm working on a kernel module which is used on plain Linux and Xenomai (RTDM), while reviewing RTDM to understand refcounting I found something that is not entirely clear to me. Why does __rtdm_dev_open() not grab a reference on the RTDM module owner? This leads to the case where one can