RTEMS | aarch64/xilinx-zynqmp: Use FDT to define PCIe memory mappings (!1116)

[SHIVAM DEOLANKAR (@D3athSkulll)]

SHIVAM DEOLANKAR commented on a discussion on bsps/aarch64/xilinx-zynqmp/start/bspstart.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1116#note_146264

 >  #include <bsp/ecc_priv.h>
 >  #include <bsp/irq-generic.h>
 >  #include <bsp/linker-symbols.h>
 > +#include <bsp/aarch64-mmu.h>
 > +#include <bsp/fdt.h>
 > +#include <libfdt.h>
 > +
 > +/*
 > + * Initialize PCIe MMU mapping using the device tree.
 > + *
 > + * Example PCIe node in the device tree:
 > + *
 > + * pcie at fd0e0000 {
 > + *     compatible = "xlnx,zynqmp-pcie";

The example PCIe node in the comment is based on the bindings used in upstream Linux device trees for ZynqMP (e.g., `xlnx,zynqmp-pcie`) and reflects the standard `ranges` property format used for PCIe host controllers. The intention is only to illustrate the expected structure for parsing, not to introduce a new or BSP-specific DT format.

If preferred, I can update the comment to more closely match a specific upstream Linux or FreeBSD DTS example

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1116#note_146264
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/20260319/e00005c9/attachment.htm>