RTEMS | fdt01: Warnings from dts used (#5653)

[Wayne Thornton (@wmthornton-dev)]

Wayne Thornton commented: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5653#note_154887


Hey @joel ,

Looking at those warnings, this comes down to newer versions of dtc enforcing stricter Device Tree Specification linting rules against that older Microblaze .dts file. Specifically, two syntax conventions are getting flagged:

Generic Node Naming (`spi_bus_bridge`): Modern specs require node names to describe the general class of hardware rather than the specific model name. The linter wants `/amba_pl/axi_quad_spi at 44a00000` to be named something generic like `spi at 44a00000`. Because that node violates the naming convention, the subsequent `spi_bus_reg` prerequisite check ends up failing as well.

Phandle References (`clocks_property`): In modern DTS syntax, a `clocks` property has to point to a valid clock controller node using a `phandle` reference (e.g., `clocks = <&clk_ctrl 0>;`). The Microblaze file has raw integers or unreferenced cells in those fields, which trips up the linter.

Since these are just dtc style/syntax warnings rather than compiler errors, the .dtb still generates and doesn't trigger a build failure.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5653#note_154887
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/4-ae3ka6fi0cewmzwghd8hot5uq-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260719/604162f0/attachment-0001.htm>