Re: Use of rtems_fdt_* and sp01

On 18/11/2022 06:32, Kinsey Moore wrote: On Thu, Nov 17, 2022 at 4:49 PM Chris Johns > wrote: On 18/11/2022 2:39 am, Kinsey Moore wrote: > I recently added FDT support to the AArch64 ZynqMP BSPs to support an optional > management console and managing e

Re: Use of rtems_fdt_* and sp01

On Thu, Nov 17, 2022 at 4:49 PM Chris Johns wrote: > On 18/11/2022 2:39 am, Kinsey Moore wrote: > > I recently added FDT support to the AArch64 ZynqMP BSPs to support an > optional > > management console and managing ethernet parameters for LibBSD. Use of > the > > rtems_fdt_* functions implies u

Re: Use of rtems_fdt_* and sp01

On 18/11/2022 2:39 am, Kinsey Moore wrote: > I recently added FDT support to the AArch64 ZynqMP BSPs to support an optional > management console and managing ethernet parameters for LibBSD. Use of the > rtems_fdt_* functions implies use of malloc which adds 4 bytes in the TLS > space. > The sp01 t

[PATCH] bsps/zynqmp: Use direct fdt_* calls

This changes the ZynqMP device tree parsing over to direct libfdt calls to avoid inclusion of malloc() in the base BSP which currently causes sp01 to fail due to unexpected use of TLS space. --- bsps/aarch64/xilinx-zynqmp/console/console.c | 32 ++-- 1 file changed, 10 insertions(+

Use of rtems_fdt_* and sp01

I recently added FDT support to the AArch64 ZynqMP BSPs to support an optional management console and managing ethernet parameters for LibBSD. Use of the rtems_fdt_* functions implies use of malloc which adds 4 bytes in the TLS space. The sp01 test uses rtems_task_construct and specifies a maxim

Re: [PATCH] icpp remedy

Dear all, To make a formal description of the bug/mismatch of implemented protocol(s), we prepared a ticket in https://devel.rtems.org/ticket/4742#no2, which contains the bug description and counter example. I hope it can help to give us a clear overview of the bug/mismatch that we found. Best, J