Re: why must POSIX_Init() call exit() rather than use a "return" statement?

On 07/05/2019 16:53, Morgan, Keith S wrote: On Monday, May 6, 2019 11:10 PM Sebastian Huber wrote: Calling exit() and returning from a POSIX thread are two totally different things. If you call exit(), then you terminate the system. If you return from a POSIX thread, then this thread exits.

Re: libbsd network stack optimization tips & tricks

On 07/05/2019 18:39, Jonathan Brandmeyer wrote: On Mon, May 6, 2019 at 12:16 AM Sebastian Huber wrote: Some known problems are: 1. RTEMS is supposed to be a real-time operating system and this has some implications for the mutex synchronization primitives. In RTEMS an atomic read-modify-write

Re: libbsd network stack optimization tips & tricks

On Mon, May 6, 2019 at 12:16 AM Sebastian Huber wrote: > > Some known problems are: > > 1. RTEMS is supposed to be a real-time operating system and this has > some implications for the mutex synchronization primitives. In RTEMS an > atomic read-modify-write operation is used in the fast path mutex

Re: rtems_binary_semaphore_post from IRQ handler

On Tue, May 7, 2019, 11:11 AM Ярослав Лещинский wrote: > problem solved: that was silly mistake related to the task min size. > Stack minimum? > > Thanks for your support, guys. > > On Mon, 6 May 2019 at 17:16, Ярослав Лещинский > wrote: > >> Hello again, >> >> >>Maybe >> >>this is related to

Re: rtems_binary_semaphore_post from IRQ handler

problem solved: that was silly mistake related to the task min size. Thanks for your support, guys. On Mon, 6 May 2019 at 17:16, Ярослав Лещинский wrote: > Hello again, > > >>Maybe > >>this is related to an interrupt with a too high priority, see also: > >>https://lists.rtems.org/pipermail/user

Re: RTEMS_FATAL_SOURCE_EXCEPTION in RTEMS

Hi Chris, > On 6/5/19 5:30 pm, Amarnath MB wrote: > >> On 3/5/19 7:04 pm, Christian Mauderer wrote: > >> > It's still odd why the PC was on some flash address. > >> Yes. The SR (below) is `CPSR = 0x20d2`. The mode is 0x12 which is > >> IRQ mode and both the I and F bits are set which means int

RE: why must POSIX_Init() call exit() rather than use a "return" statement?

On Monday, May 6, 2019 11:10 PM Sebastian Huber wrote: > Calling exit() and returning from a POSIX thread are two totally different > things. > If you call exit(), then you terminate the system. If you return from a POSIX > thread, then this thread exits. The scheduler just picks up the next hi