Good morning Sebastian,
thanks for your quick answer. Thanks for your hint on where to look for
the locking. I think i will need some time to understand what each macro
is doing.
My plan with the rtems_task_mode() call was to start there and trace
down to the according kernel call.
I will try th
On 13/11/2018 09:37, Malte Münch wrote:
Good morning Sebastian,
thanks for your quick answer. Thanks for your hint on where to look for
the locking. I think i will need some time to understand what each macro
is doing.
My plan with the rtems_task_mode() call was to start there and trace
down to
On 13/11/2018 09:58, Malte Münch wrote:
ok, so if i get this right _Thread_Dispatch_disable() and disabling of
interrupts both ensure that the current thread is not preempted and can
continue its spinning as it is waiting for its resource. As is seems to
me _Thread_Dispatch_disable is the better
Hi Sebastian,
This is great for our application code that includes rtems.h.
Thanks,
Alan
On 11/12/18, 11:04 AM, "Sebastian Huber"
wrote:
Hello Alan,
I removed several internal data types from . Now, it is
possible to include in -std=c99 mode.
https://devel.rtems.o
Hello,
the RSB uses now GCC 9 to for the or1k tool chain:
https://git.rtems.org/rtems-source-builder/commit/?id=8241563b6ec559fd562ec41147b04797a54dfe5f
I was able to build this RTEMS BSP with it and link the tests:
https://git.rtems.org/rtems/commit/?id=28bf4cae7878f4e47cc24c114fc9c5567247ecc
