Re: Node vs Threads in scheduling

On 17/08/2020 14:35, Richi Dubey wrote: Also, can someone please explain how the thread could in the ready state while the node is in a scheduled state in this conditional block ? The MrsP locking

Re: Node vs Threads in scheduling

Thank you. On Tue, Aug 18, 2020 at 5:29 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 17/08/2020 14:35, Richi Dubey wrote: > > > Also, can someone please explain how the thread could in the ready > > state while the node is in a scheduled state in this > > < >

Re: Node vs Threads in scheduling

On 17/08/2020 14:35, Richi Dubey wrote: Also, can someone please explain how the thread could in the ready state while the node is in a scheduled state in this conditional block ? The MrsP locking

Re: [PATCH] bsps/shared/ofw: Implement RTEMS OFW interface

How can we make this API FreeBSD compatible? We have to declare defines for the OFW functions Eg. #define OF_finddevice rtems_ofw_find_device Should I change the openfirm.h in libBSD to this use these defines instead of calling the functions in openfirm.c? Though there are some functions which

[PATCH] build: Use Python tarfile instead of pax

This patch is for the new build system. --- spec/build/testsuites/libtests/dl01.yml | 2 +- spec/build/testsuites/libtests/dl02.yml | 2 +- spec/build/testsuites/libtests/dl04.yml | 2 +- spec/build/testsuites/libtests/dl05.yml | 2 +- spec/build/testsuites/libtests/dl06.yml | 4

Re: [PATCH] bsps/shared/ofw: Implement RTEMS OFW interface

On 18/08/2020 11:25, Niteesh G. S. wrote: > How can we make this API FreeBSD compatible? We have to declare > defines for the OFW functions > Eg. #define OF_finddevice rtems_ofw_find_device I think that was the plan, wasn't it? > > Should I change the openfirm.h in libBSD to this use these

[PATCH] psxkey01: Fix configuration

From: Aschref Ben Thabet Key_ID array must have the right size, it shall have a value greater than zero. Note: In Standard C and C++, zero-size array is not allowed.. --- testsuites/psxtests/psxkey01/system.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

How to schedule a node on a different processor?

Hi, This question is wrt the use of Scheduler_SMP_Preempt here . This function eventually calls Allocate_Processor and while tracing with gdb, everything is going as I

[PATCH] Fix -Wchar-subscripts warnings

From: Aschref Ben Thabet The argument to the ctype functions must be an int and the value of the character must be representable as an unsigned char or equal to the value of the macro EOF. If the argument has any other value, the behavior is undefined. --- cpukit/libdl/rtl-archive.c

Re: How to schedule a node on a different processor?

On Tue, Aug 18, 2020 at 9:21 AM Richi Dubey wrote: > > Hi, > > This question is wrt the use of Scheduler_SMP_Preempt here. This function > eventually calls Allocate_Processor and while tracing with gdb, everything is > going as I planned, i.e. the correct node is getting preempted and the

Re: [PATCH] build: Use Python tarfile instead of pax

On 18/8/20 9:16 pm, Sebastian Huber wrote: > This patch is for the new build system. Looking forward to this change. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] bsps/shared/ofw: Implement RTEMS OFW interface

On Tue, Aug 18, 2020 at 8:26 PM Christian Mauderer wrote: > On 18/08/2020 11:25, Niteesh G. S. wrote: > > How can we make this API FreeBSD compatible? We have to declare > > defines for the OFW functions > > Eg. #define OF_finddevice rtems_ofw_find_device > > I think that was the plan, wasn't

Re: [PATCH] bsps/shared/ofw: Implement RTEMS OFW interface

On Tue, Aug 18, 2020 at 12:07 PM Christian Mauderer wrote: > > On 18/08/2020 19:01, Niteesh G. S. wrote: > > > > > > On Tue, Aug 18, 2020 at 8:26 PM Christian Mauderer > > wrote: > > > > On 18/08/2020 11:25, Niteesh G. S. wrote: > > > How can we make this API

Re: How to schedule a node on a different processor?

On Tue, Aug 18, 2020 at 11:20 AM Richi Dubey wrote: > > Hi, > > Thanks for the help. I looked at the call trace and figured out what is wrong. > > As we had discussed earlier, We would be changing the passed variable > filter_base pointer (done here) to the function >

Re: How to schedule a node on a different processor?

Hi, Thanks for the help. I looked at the call trace and figured out what is wrong. As we had discussed earlier, We would be changing the passed variable filter_base pointer (done here

Re: [PATCH] bsps/shared/ofw: Implement RTEMS OFW interface

On 18/08/2020 19:01, Niteesh G. S. wrote: > > > On Tue, Aug 18, 2020 at 8:26 PM Christian Mauderer > wrote: > > On 18/08/2020 11:25, Niteesh G. S. wrote: > > How can we make this API FreeBSD compatible? We have to declare > > defines for the OFW functions

Re: [GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

Hi Mritunjay, To define the architecture you can create a file “CONFIG_SITE.local” in “configure”. Look at the comment at the end of the file "CONFIG_SITE": " ... # Overrides for the settings above may appear in a CONFIG_SITE.local file -include $(CONFIG)/CONFIG_SITE.local. “ Heinz > On 16.

Re: [GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

On Tue, Aug 18, 2020 at 7:13 PM Heinz Junkes wrote: > > Hi Mritunjay, > > To define the architecture you can create a file “CONFIG_SITE.local” in > “configure”. > Look at the comment at the end of the file "CONFIG_SITE": > > " > ... > # Overrides for the settings above may appear in a

[PATCH] ada: Add missing attributes

--- cpukit/include/adainclude/rtems.ads | 9 + 1 file changed, 9 insertions(+) diff --git a/cpukit/include/adainclude/rtems.ads b/cpukit/include/adainclude/rtems.ads index 5069c36011..0b4b3e7e5f 100644 --- a/cpukit/include/adainclude/rtems.ads +++ b/cpukit/include/adainclude/rtems.ads

Re: [GSoC 2020]: Need help in writing sed alternative in Python for RSB recipes

Hi everyone, Before I begin my queries [ mainly regarding epics upstream], let me give a few updates. As per the suggestion of Gedare, I started building by hand the pc-386 and xilinx_zynq_a9_qemu using the terminal configured make command. What I did initially as an experiment is that, in