You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by GitBox <gi...@apache.org> on 2020/05/10 14:45:57 UTC

[GitHub] [incubator-nuttx] xiaoxiang781216 commented on issue #1020: [RFC] Using devicetree (DTS) to improve board support

xiaoxiang781216 commented on issue #1020:
URL: https://github.com/apache/incubator-nuttx/issues/1020#issuecomment-626339275


   So, you plan to generate the source code from device tree? The device tree concept disappear after the tool finish the conversion.
   This approach is totally different from Linux which I am working with more than five years. Did you studied how device tree is used in other OS(e.g. Linux or Zephyr) and summary pros and cons for the different approach?
   I am working with Linux kernel more than ten years, the most important design decision for Linux driver from my view is just two things:
   1.Introduce the common driver model from 2000~:
      https://www.kernel.org/doc/html/latest/driver-api/driver-model/index.html
   2.Inroduce the device tree from 2010~:
      https://github.com/torvalds/linux/blob/master/Documentation/devicetree/usage-model.txt
      https://github.com/torvalds/linux/blob/master/Documentation/devicetree/booting-without-of.txt
   And give me a strong impresson how Linux combine these two piece concept in a flexiable way and fix many driver problems I found ten years ago with a a elegant solution.
   So I would sugest to study how other OS(at least Linux and Zephy) use the device tree before we start porting the device tree to NuttX.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org