RTEMS | riscv: use configured RAM region if defined (!1181)

[Kinsey Moore (@opticron)]

Kinsey Moore started a new discussion on bsps/riscv/shared/start/bspgetworkarea.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1181#note_147954

 >  static void bsp_memory_initialize( void )
 >  {
 >    void *end;
 > +#if defined(RISCV_RAM_REGION_BEGIN) && defined(RISCV_RAM_REGION_SIZE)
 > +  uintptr_t start = RISCV_RAM_REGION_BEGIN;
 > +  uintptr_t size = RISCV_RAM_REGION_SIZE;
 > +  end = (void*) start + size;
 > +#else

It seems that the niosv BSP would be the only one unaffected by this, but only because it has its own option names for its external and on-chip RAM. For the niosv, only the external RAM is currently used in the linker script. The niosv BSP should probably also be dealt with the same way since it doesn't support FDT at all.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1181#note_147954
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260403/95be7b2c/attachment.htm>