Re: [PATCH] build: Add PROGRAM_PREFIX option

On 04.08.23 00:27, Chris Johns wrote: On 2/8/2023 6:49 pm, Chris Johns wrote: > I am concerned about the compatibility to the ecosystem we have. Have you built all the tests in the testsuite with this value set to something that is not RTEMS default? I think a few things will break because

Re: [PATCH] libdebugger: Restrict ARM architecture support

On 04.08.23 00:43, Chris Johns wrote: On 3/8/2023 10:17 pm, Sebastian Huber wrote: Build the arm libdebugger support only for supported ARM architectures. What ARM archs are not supported? At least ARMv7-M and everything with Thumb 1. This fixes assembler errors at -O0. How does it fix

Re: [PATCH] trace/wscript: Improve C++ standard selection

On 04.08.23 00:53, Chris Johns wrote: On 3/8/2023 5:36 pm, Sebastian Huber wrote: Ping. Which repo? Is this in the rtems-tools repo? Yes, the rtems-tools. Please understand there is a limited number people reviewing and it takes time. I am blocked on the other changes you have recently

Re: [PATCH] trace/wscript: Improve C++ standard selection

On 3/8/2023 5:36 pm, Sebastian Huber wrote: > Ping. Which repo? Is this in the rtems-tools repo? Please understand there is a limited number people reviewing and it takes time. I am blocked on the other changes you have recently posted. Adding which hosts you have built and tested this change on

Re: [PATCH] 6: Use Binutils 2.41

On 3/8/2023 5:37 pm, Sebastian Huber wrote: > What about this patch and the GCC update to 13.2? I have not tested it. Have you posted any build results to builds@rtems...? Chris ___ devel mailing list devel@rtems.org

Re: [PATCH] libdebugger: Restrict ARM architecture support

On 3/8/2023 10:17 pm, Sebastian Huber wrote: > Build the arm libdebugger support only for supported ARM architectures. What ARM archs are not supported? > This fixes assembler errors at -O0. How does it fix the assembler errors? Chris ___ devel

Re: [PATCH] build: Add PROGRAM_PREFIX option

On 2/8/2023 6:49 pm, Chris Johns wrote: > I am concerned about the compatibility to the ecosystem we have. Have you > built > all the tests in the testsuite with this value set to something that is not > RTEMS default? I think a few things will break because of hard coding in them. I have

Re: [PATCH 1/3] Adding core-v cv32a6 support

On 03.08.23 15:29, Kevin Eyssartier wrote: This commit add support for the CV32A6 processor in the rv32imac configuration. The CORE-V CVA6 is an application class 6 stage RISC-V CPU capable of booting Linux. It support multiple configurations : ISA (IMACFDB), XLEN 32 and 64, configurable cache

Re: [PATCH 3/3] Force ISR enable before scheduler start

On 03.08.23 15:29, Kevin Eyssartier wrote: The ISR was not activated when running without RTEMS_SMP. Is there a test which fails due to this bug? Please use the already existing CPU port interface _CPU_Start_multitasking() to fix this bug. -- embedded brains GmbH Herr Sebastian HUBER

[PATCH 3/3] Force ISR enable before scheduler start

The ISR was not activated when running without RTEMS_SMP. --- cpukit/score/cpu/riscv/include/rtems/score/cpu.h | 3 +++ cpukit/score/cpu/riscv/riscv-context-switch.S| 5 + cpukit/score/src/threadstartmultitasking.c | 2 +- 3 files changed, 9 insertions(+), 1 deletion(-) diff --git

[PATCH 2/3] bsps/riscv: Handle ":" in chosen stdout-path

The riscv_get_console_node function is searching the devices for the string specified in chosen in the fdt. Unfortunately, this chosen string can contain parameters after the ":" character. As specified in https://www.kernel.org/doc/Documentation/devicetree/bindings/chosen.txt : If the

[PATCH 1/3] Adding core-v cv32a6 support

This commit add support for the CV32A6 processor in the rv32imac configuration. The CORE-V CVA6 is an application class 6 stage RISC-V CPU capable of booting Linux. It support multiple configurations : ISA (IMACFDB), XLEN 32 and 64, configurable cache size, TLBs, PTW and branch prediction. It is

[PATCH] libdebugger: Restrict ARM architecture support

Build the arm libdebugger support only for supported ARM architectures. This fixes assembler errors at -O0. Close #4939. --- cpukit/libdebugger/rtems-debugger-arm.c | 24 +--- 1 file changed, 9 insertions(+), 15 deletions(-) diff --git

Re: [PATCH] doxygen: Replace and move main page

Hello Joel, On 28.07.23 16:37, Sebastian Huber wrote: Replace the main page with a high level description of the RTEMS feature set similar to: https://docs.rtems.org/branches/master/user/overview/index.html#features The replaced content can be found in the RTEMS Classic API Guide:

Re: [PATCH] 6: Use Binutils 2.41

What about this patch and the GCC update to 13.2? On 31.07.23 08:13, Sebastian Huber wrote: Prepare for RTEMS 6.1 release. Update #4921. --- rtems/config/6/rtems-default.bset | 2 +- rtems/config/tools/rtems-binutils-2.41.cfg | 13 + 2 files changed, 14 insertions(+),

Re: [PATCH] trace/wscript: Improve C++ standard selection

Ping. On 19.05.23 07:02, Sebastian Huber wrote: Use the latest C++ standard available up to C++20. Close #4908. --- trace/wscript | 18 +++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/trace/wscript b/trace/wscript index a3dd5d5..adabd5f 100644 ---

Re: CVA6 RISC-V support

Hello, Thanks for sending out the patches. Could you please send them as emails instead of attachments? e.g., using git send-email [1]. That'll be easier to review and comment on. [1] https://docs.rtems.org/branches/master/user/support/contrib.html Regards, Hesham On Tue, 1 Aug 2023 at 16:53,