Is the Zephyr Device Tree Too Complicated? - Tim Guite, Magpie Embedded скачать в хорошем качестве

Is the Zephyr Device Tree Too Complicated? - Tim Guite, Magpie Embedded

Don't miss out! Join us at the next Open Source Summit in Seoul, South Korea (November 4-5). Join us at the premier vendor-neutral open source conference, where developers and technologists come together to collaborate, share knowledge, and explore the latest innovations and advancements in open source technology. Learn more at https://events.linuxfoundation.org/ Is the Zephyr Device Tree Too Complicated? - Tim Guite, Magpie Embedded The device tree is one of the defining characteristics of the Zephyr project. Using concepts borrowed from Linux, along with its best buddy Kconfig, it allows us to leverage the ecosystem to avoid endlessly rewriting the same drivers. It is also one of the most challenging aspects of Zephyr for developers to get their head around as they venture into the woods beyond the “Getting Started” guide. Device trees can contain repeated, redundant information and parameters which are difficult to trace back to their source. On the other hand, the device tree caters to an incredibly wide range of users who might be setting up a single accelerometer or specifying the peripheral mapping for a multi-core SoC. So, is the device tree too complicated, is it just right, or are there other ways to tackle this problem?