Sebastian Huber commented on a discussion on bsps/aarch64/shared/start/start.S: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/113#note_112207 > _el1_start: > > #ifdef RTEMS_SMP > - /* Read MPIDR and get current processor index */ > - mrs x7, mpidr_el1 > - and x7, x7, #0xff > + ldr x3, =aarch64_cpu_boot_params Yes, it could be complex, so it is important to hide this complexity behind function calls. So, instead of accessing your map from everywhere, you should define a function call based API with currently two implementations: 1. the simple one we have right now which just uses the mpidr_el1, 2. the one with this map table. A third one could use a device tree or whatever in the future. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/113#note_112207 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
