We've figured out our problem here and I wanted to update the thread to
give closure, and to make sure any future inquiring minds don't have to
wonder what was going on here.
First, we confirmed that our colleague's usage of
rtdm_waitqueue_lock/unlock was only for it's creation of an atomic
Thank you Jan, Philippe. Your responses have given us a lot to look into
and a lot to learn. We'll come back with a more detailed response once
we've gained a little more understanding on our end.
Matt
On Wed, Mar 16, 2022 at 5:09 AM Philippe Gerum wrote:
>
> Matt Klass via Xenomai writes:
>
Matt Klass via Xenomai writes:
> Using Xenomai 3.0.10, with kernel 4.9.128-05789, on armv7, we're having
> problems with the functionality of rtdm_waitqueues. The code was written by
> a Xenomai-adept developer who has since left for greener pastures.
>
> We have two functions that use
On 15.03.22 19:27, Matt Klass via Xenomai wrote:
> Using Xenomai 3.0.10, with kernel 4.9.128-05789, on armv7, we're having
> problems with the functionality of rtdm_waitqueues. The code was written by
> a Xenomai-adept developer who has since left for greener pastures.
>
> We have two functions
Using Xenomai 3.0.10, with kernel 4.9.128-05789, on armv7, we're having
problems with the functionality of rtdm_waitqueues. The code was written by
a Xenomai-adept developer who has since left for greener pastures.
We have two functions that use rtdm_waitqueue_lock/unlock on the same
