[PATCH v3 2/2] aarch64/versal: Support DDRMC0 region 0 and 1

From: Chris Johns - Support DDRMC0 region 0 up to 2G in size - Support DDRMC0 region 1 with DDR memory greater than 2G up to the DDRMC0 max amount - Extend the heap with region 1's memory Closes #4684 --- bsps/aarch64/xilinx-versal/include/bsp.h | 9

[PATCH v3 1/2] basp/aarch64: Make the unexpected sections origin address 64bit

From: Chris Johns Update #4684 --- bsps/aarch64/shared/start/linkcmds.base | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bsps/aarch64/shared/start/linkcmds.base b/bsps/aarch64/shared/start/linkcmds.base index bcdf4715d7..f4639bd990 100644 ---

[PATCH v3] aarch64/versal: Support DDRMC0 region 0 and 1

Hi, The Versal's DDRMC0 supports two separate regions. Region 0 is from 0 up to 2G where the Versal's hard IP regions start. DDR memory above the 2G mark is moved to region 1 and its base address is in the A64 address space. The patch will place all memory up to 2G in region 0 and if more is

Re: [PATCH 2/2] aarch64/versal: Support DDRMC0 region 0 and 1

On 26/7/2022 11:47 pm, Kinsey Moore wrote: > On 7/22/2022 01:35, chr...@rtems.org wrote: >> From: Chris Johns >> >> - Support DDRMC0 region 0 up to 2G in size >> >> - Support DDRMC0 region 1 with DDR memory greater than 2G >>    up to the DDRMC0 max amount >> >> - Extend the heap with region 1's

Re: [tools v2] tester: Normalize JSON and YAML reports

OK and thanks. Chris On 26/7/2022 10:10 pm, Sebastian Huber wrote: > Report the same data in JSON and YAML reports. Do not report redundant > information. > > Update 4671. > --- > v2: > > * Add 'report-version' attribute with a value of 1. > > * Add 'tester-version' attribute. > > * Use a

Re: [tools v2] tester: Normalize JSON and YAML reports

Looks good. The previous format was definitely tied too heavily to the RTEMS internal testsuite and this makes it easier to apply to other tests. Kinsey On 7/26/2022 07:10, Sebastian Huber wrote: Report the same data in JSON and YAML reports. Do not report redundant information. Update

arm/lpc1768_mbed_ahb_ram_eth failures was Fwd: [rtems-bsp-builder] 2022-07-26 05:55:28: Profile(s): everything

Hi The arm/lpc1768_mbed_ahb_ram_eth BSP has 6 configurations which can't build and link all the tests. --joel -- Forwarded message - From: OAR Tester Date: Tue, Jul 26, 2022 at 9:52 AM Subject: [rtems-bsp-builder] 2022-07-26 05:55:28: Profile(s): everything To: RTEMS Tools

Re: [PATCH 2/2] aarch64/versal: Support DDRMC0 region 0 and 1

On 7/22/2022 01:35, chr...@rtems.org wrote: From: Chris Johns - Support DDRMC0 region 0 up to 2G in size - Support DDRMC0 region 1 with DDR memory greater than 2G up to the DDRMC0 max amount - Extend the heap with region 1's memory Closes #4684 ---

Re: [PATCH 1/2] basp/aarch64: Make the unexpected sections origin address 64bit

On 7/25/2022 20:56, Chris Johns wrote: On 25/7/2022 2:00 pm, Kinsey Moore wrote: On 7/24/2022 17:04, Chris Johns wrote: On 22/7/2022 11:14 pm, Kinsey Moore wrote: Has this patch been tested with ILP32? I suspect that this line might need to get yanked out to a shared lp64 linkcmds.base and a

Re: [tools] tester: Normalize JSON and YAML reports

Hello, I sent a v2 of the patch: https://lists.rtems.org/pipermail/devel/2022-July/072679.html On 01/07/2022 01:12, Chris Johns wrote: From my point of view the JSON/YAML reports should not satisfy every possible consumer directly. How do you determine the list you are satisfying? I can see

[tools v2] tester: Normalize JSON and YAML reports

Report the same data in JSON and YAML reports. Do not report redundant information. Update 4671. --- v2: * Add 'report-version' attribute with a value of 1. * Add 'tester-version' attribute. * Use a list for both 'command-line' attributes. tester/rt/test.py | 193

Re: [PATCH v3 2/2] bsp/riscv: Add NOEL-V BSP

On 15/07/2022 14:54, Sebastian Huber wrote: diff --git a/spec/build/bsps/riscv/noel/optextirqmax.yml b/spec/build/bsps/riscv/noel/optextirqmax.yml new file mode 100644 index 00..ffa84748b6 --- /dev/null +++ b/spec/build/bsps/riscv/noel/optextirqmax.yml @@ -0,0 +1,16 @@

[PATCH] c-user: Document new rtems_task_delete() behaviour

Update #4679. --- c-user/task/directives.rst | 29 +++-- 1 file changed, 23 insertions(+), 6 deletions(-) diff --git a/c-user/task/directives.rst b/c-user/task/directives.rst index 64b591d..9f9ea45 100644 --- a/c-user/task/directives.rst +++ b/c-user/task/directives.rst

Re: [PATCH] score: Remove PRIORITY_PSEUDO_ISR thread priority

On 22/07/2022 14:35, Sebastian Huber wrote: On 21.07.22 16:20, Joel Sherrill wrote: On Thu, Jul 21, 2022 at 12:53 AM Sebastian Huber > wrote:     Hello Gedare and Joel,     On 15.07.22 10:43, Sebastian Huber wrote: > The uniprocessor

Re: AW: [PATCH] sppps01: Add test case for early returns of pps_event()

Hello Gabriel, On 26/07/2022 10:03, gabriel.moy...@dlr.de wrote: The patch added a new test case (PPSEventEarlyReturns) for increasing the test coverage. The test case checks whether the function pps_event() (in file kern_tc.c) returns early. According to the result you shared, the test is

AW: [PATCH] sppps01: Add test case for early returns of pps_event()

Hi Kinsey, Sorry for the late response, I wasn't available. The patch added a new test case (PPSEventEarlyReturns) for increasing the test coverage. The test case checks whether the function pps_event() (in file kern_tc.c) returns early. According to the result you shared, the test is failing

Re: [PATCH v4 3/7] bsps: Add GPIO API

On 25/7/2022 11:54 am, Duc Doan wrote: > Hello, > > On Mon, 2022-07-25 at 11:42 +1000, Chris Johns wrote: >> On 23/7/2022 1:53 pm, Duc Doan wrote: >>> This is the new GPIO API. The header file is >>> gpio2.h. >>> --- >>>  bsps/include/bsp/gpio2.h    | 526 >>>