Re: INTR-REMAP error with UDD driver

2019-03-07 Thread Jan Kiszka via Xenomai
On 08.03.19 02:35, Jeff Webb via Xenomai wrote: I have implemented a simple UDD mini-driver (interrupt handler) and an associated Xenomai userspace test program. This pair of programs works as intended on one machine. When I tried running the same programs on another machine, I got this erro

INTR-REMAP error with UDD driver

2019-03-07 Thread Jeff Webb via Xenomai
I have implemented a simple UDD mini-driver (interrupt handler) and an associated Xenomai userspace test program. This pair of programs works as intended on one machine. When I tried running the same programs on another machine, I got this error when the first interrupt occurred: kernel: [

Re: PCI UDD Questions

2019-03-07 Thread Jeff Webb via Xenomai
On Wednesday, March 6, 2019 11:38 AM, Jan Kiszka wrote: > On 06.03.19 12:24, Philippe Gerum via Xenomai wrote: > > > On 3/2/19 1:25 PM, Jeff Webb via Xenomai wrote: > > > > > I could also avoid using the PCI command register entirely and just write > > > to a device-specific mask bit in my perip

smokey's fork tests hangs?

2019-03-07 Thread Lange Norbert via Xenomai
Hello, I have problems with the fork tests, they both hang for me. # xeno smokey --run=11 --verbose=2 # xeno smokey --run=20 --verbose=2 no leak withthread no leak withmutex no leak withcond no leak withsem no leak withnamed sem no leak withtimer no leak withmq When started under gdb, the par

[PATCH v2 2/5] libcobalt: improve documentation regarding mutex initializers

2019-03-07 Thread Norbert Lange via Xenomai
Signed-off-by: Norbert Lange --- lib/cobalt/mutex.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/lib/cobalt/mutex.c b/lib/cobalt/mutex.c index be9f6ed80..125981d40 100644 --- a/lib/cobalt/mutex.c +++ b/lib/cobalt/mutex.c @@ -49,8 +49,12 @@ * By default, Cobalt mut

[PATCH v2 5/5] smokey: add tests for mutex/condvar autoinit

2019-03-07 Thread Norbert Lange via Xenomai
add a few testcases where destroy is called as first function, and test failure if the state is a non-standard initializer. Signed-off-by: Norbert Lange --- testsuite/smokey/posix-cond/posix-cond.c | 14 +++ testsuite/smokey/posix-mutex/posix-mutex.c | 47 ++ 2 files ch

[PATCH v2 4/5] libcobalt: improve documentation regarding condvar initializers

2019-03-07 Thread Norbert Lange via Xenomai
Signed-off-by: Norbert Lange --- lib/cobalt/cond.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/lib/cobalt/cond.c b/lib/cobalt/cond.c index 92eb230ff..cdbd512ae 100644 --- a/lib/cobalt/cond.c +++ b/lib/cobalt/cond.c @@ -47,9 +47,13 @@ * several processes (it ma

[PATCH v2 3/5] libcobalt: improve condvar autoinit support

2019-03-07 Thread Norbert Lange via Xenomai
contrary to some comments, condvars are automatically initialised on signal/wait. Correct the destroy method to not report an error on such condvars. Check whether the condition variable has the static initializer is now more strict. Signed-off-by: Norbert Lange --- lib/cobalt/cond.c | 93 +

[PATCH v2 1/5] libcobalt: improve mutex autoinit support

2019-03-07 Thread Norbert Lange via Xenomai
contrary to some comments, mutexes are automatically initialised on lock/unlock. Correct the destroy method to not report an error on such mutexes. {get,set}prioceiling requires mutexes that were explicitely initialised, so no change needed there Signed-off-by: Norbert Lange --- lib/cobalt/mute

[no subject]

2019-03-07 Thread Norbert Lange via Xenomai
This is V2 as the first version had alot unnecessary whitespace changes (otherwise empty lines with ws removed)

[PATCH 5/5] smokey: add tests for mutex/condvar autoinit

2019-03-07 Thread Norbert Lange via Xenomai
add a few testcases whete dstroy is called as first function, and test failure if the state is a non-standard initializater. Signed-off-by: Norbert Lange --- testsuite/smokey/posix-cond/posix-cond.c | 14 testsuite/smokey/posix-mutex/posix-mutex.c | 93 -- 2 files chan

[PATCH 4/5] libcobalt: improve documentation regarding condvar initializers

2019-03-07 Thread Norbert Lange via Xenomai
Signed-off-by: Norbert Lange --- lib/cobalt/cond.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/lib/cobalt/cond.c b/lib/cobalt/cond.c index 92eb230ff..cdbd512ae 100644 --- a/lib/cobalt/cond.c +++ b/lib/cobalt/cond.c @@ -47,9 +47,13 @@ * several processes (it ma

[PATCH 2/5] libcobalt: improve documentation regarding mutex initializers

2019-03-07 Thread Norbert Lange via Xenomai
Signed-off-by: Norbert Lange --- lib/cobalt/mutex.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/lib/cobalt/mutex.c b/lib/cobalt/mutex.c index be9f6ed80..125981d40 100644 --- a/lib/cobalt/mutex.c +++ b/lib/cobalt/mutex.c @@ -49,8 +49,12 @@ * By default, Cobalt mut

[PATCH 3/5] libcobalt: improve condvar autoinit support

2019-03-07 Thread Norbert Lange via Xenomai
contrary to some comments, condvars are automatically initialised on signal/wait. Correct the destroy method to not report an error on such condvars. Check whether the condition variable has the static initializer is now more strict. Signed-off-by: Norbert Lange --- lib/cobalt/cond.c | 93 +

[PATCH 1/5] libcobalt: improve mutex autoinit support

2019-03-07 Thread Norbert Lange via Xenomai
contrary to some comments, mutexes are automatically initialised on lock/unlock. Correct the destroy method to not report an error on such mutexes. {get,set}prioceiling requires mutexes that were explicitely initialised, so no change needed there Signed-off-by: Norbert Lange --- lib/cobalt/mute