Re: Doubt regarding thread creation in RTEMS

Hi, _Thread_Clear_state_locked( the_thread, STATES_ALL_SET ); I did have a look at it, it unblocks the node belonging to the_thread, I'll go through everything again. When you use the debugger to figure out what is going on I would step in > to each function you don't know. Got it. Thank you.

Re: Benchmarking RTEMS on PPC vs ARM multicore

Hello Gedare, what kind of performance benchmarking do you have in mind? To benchmark the clustered scheduling, you need at least a system with separated L2 caches, e.g. T4240 and LS1088A. We don't have BSPs for the QorIQ Layerscape platform. The chips are quite complex. I haven't looked c

RE: [PATCH v1 0/1] bsps/pc386: Fix IPI for non-consecutive Apic IDs

> -Original Message- > From: Gedare Bloom [mailto:ged...@rtems.org] > Sent: Monday, July 20, 2020 10:12 PM > To: Sommer, Jan > Cc: devel@rtems.org > Subject: Re: [PATCH v1 0/1] bsps/pc386: Fix IPI for non-consecutive Apic IDs > > Hi Jan, > > Slightly off-topic, but which Intel Atom board

Re: [PATCH v1 0/1] bsps/pc386: Fix IPI for non-consecutive Apic IDs

Hi Jan, Slightly off-topic, but which Intel Atom board are you using? If you can say, and if your board has non-legacy boot, how did you get through the boot sequence? That has been a trouble for some folks before. Gedare On Fri, Jul 3, 2020 at 6:32 AM Jan Sommer wrote: > > Hi, > > I had some t

Benchmarking RTEMS on PPC vs ARM multicore

Hi Sebastian et al., I might get a chance to do some performance benchmarking of RTEMS on multicore platforms in the near future. I'm looking at the possibility to compare PPC and ARM boards that are roughly similar in capability. I was hoping someone with a bit of domain expertise could help me t

Re: [PATCH rtems v2 3/3] bsps/fdt: Make sure data is cache aligned.

looks good if it works, thanks Christian! On Sun, Jul 19, 2020 at 11:47 PM Christian Mauderer wrote: > > The cache of the fdt blob is flushed after copy. Therefore it should be > aligned. > --- > bsps/shared/start/bsp-fdt.c | 8 +--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > diff

Re: [PATCH v3] Fix warning in isspace() and isdigit().

Hello Aschref, please use v3 only for the third version of a patch. This is a new patch. To avoid confusion please use distinctive subjects. Please fix also the coding style in this patch. Since this change is similar to the first patch, maybe these two patches should be just one. You can co

Re: Doubt regarding thread creation in RTEMS

On 20/07/2020 17:16, Richi Dubey wrote: Hi, I am trying to map out how a task gets scheduled according to a scheduling algorithm once a user writes rtems_task_create() and later rtems_task_start() in the source file. On debugging with gdb, I came to realize that the rtems_task_start() func

[PATCH v3] Fix warning in isspace() and isdigit().

From: Aschref Ben Thabet The warning may be because you're passing a char to the isspace() macro. The implementation of isspace() may be via array indexing. (The argument to the isspace()/isdegit() macro is defined to be an unsigned char the value of which can fit in an unsignedchar). at ctype.h

Doubt regarding thread creation in RTEMS

Hi, I am trying to map out how a task gets scheduled according to a scheduling algorithm once a user writes rtems_task_create() and later rtems_task_start() in the source file. On debugging with gdb, I came to realize that the rtems_task_start() function calls _Thread_Start() (cpukit/rtems/src/t

[PATCH v2] Fix warning in isspace() and isdigit().

From: Aschref Ben Thabet The warning may be because you're passing a char to the isspace() macro. The implementation of isspace() may be via array indexing. (The argument to the isspace()/isdegit() macro is defined to be an unsigned char the value of which can fit in an unsignedchar). at ctype.h

Re: [PATCH] The warning may be because you're passing a char to the isspace() macro. The implementation of isspace() may be via array indexing. (The argument to the isspace()/isdegit() macro is define

Hello Aschref, please fix the format of the commit message to be in line with standard line length limits for the subject and the text body: https://chris.beams.io/posts/git-commit/ On 20/07/2020 15:53, Aschref Ben-Thabet wrote: From: Aschref Ben Thabet at ctype.h in GNU libc, and while th

[PATCH] The warning may be because you're passing a char to the isspace() macro. The implementation of isspace() may be via array indexing. (The argument to the isspace()/isdegit() macro is defined to

From: Aschref Ben Thabet at ctype.h in GNU libc, and while there's a complicated mess of macros and functions, somewhere in the definition of isspace() there's an array being indexed. See if isspace((unsigned char) *str) gets rid of the warning. The line array[c] is very likely a bug, because

Re: A question about rtems license

Hello, since the GPLv2 with the linking exception is a bit hard to understand there is an RTEMS Project goal to re-license RTEMS to BSD-2-Clause: https://devel.rtems.org/ticket/3053 All core developers already agreed to the license change. It is a bit tedious to carry out the re-licensing wo