RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

[Kinsey Moore (@opticron)]

Kinsey Moore commented on a discussion on spec/build/bsps/arm/xilinx-zynqmp-rpu/optmematcmbtcm.yml: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112376

 > -- assert-uint32: null
 > +- get-string: null
 >  - env-assign: null
 > -- format-and-define: null
 >  build-type: option
 >  copyrights:
 > -- Copyright (C) 2020 embedded brains GmbH & Co. KG
 > +- Copyright (C) 2024 embedded brains GmbH & Co. KG
 >  default:
 > +- enabled-by: ZYNQMP_RPU_LOCK_STEP_MODE
 > +  value: ATCM
 >  - enabled-by: true
 > -  value: 0x00100000
 > -description: ''
 > +  value: BTCM
 > +description: null

Given that it's not supposed to be user-visible, this form of the logic doesn't provide documentation, and it's only used in one place, is there a reason it isn't a conditional in the linker script?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112376
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/20240920/90bb8cf1/attachment.htm>