SHIVAM DEOLANKAR commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5510#note_145114 Thank you for the clarification. The intention of this change is not to introduce a new FDT framework or BSP-specific approach. The implementation only reads the PCIe `ranges` property from the existing BSP FDT when present. If the PCIe node is not available, the code falls back to the previous static MMU mappings, preserving the original BSP behaviour. This keeps the change localized to the ZynqMP BSP without affecting other BSPs or introducing a new FDT handling model. I agree that a common FDT framework would be beneficial for broader use across RTEMS BSPs. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5510#note_145114 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
