On Fri, May 6, 2016 at 4:30 AM, Nicolas Ferre <nicolas.ferre@xxxxxxxxx> wrote: > Le 06/05/2016 11:16, Phil Elwell a écrit : >>> In the wild where? >>> >>> IMO, too bad. That's the danger of deploying prototype code. Perhaps a >>> tool to convert them would be better. > > Prototype code or no code, which one solve actual problems? I didn't say don't use it. You just have to understand the risks when you take things off the list and be willing to deal with the changes. In any case, we're only talking about changes in the source format. Anything deployed should be fine. Folks can't update their dts files? >> At Raspberry Pi we've been making good use of overlays for over a year now. >> They have been an invaluable tool, allowing us to reduce the need for >> downstream code while retaining and extending the flexibility our users >> need. Without the circulating patches I would have pressed ahead with a >> homegrown equivalent, which would have made switching to overlays much more >> painful. And I'm glad you did. It works great for me. >> I hope to see Pantelis's overlay configfs code in a kernel release soon, >> but until then we'll continue to apply the patches downstream. > > +1 > > Same situation for for Atmel Xplained boards. > I remember having identified DT overlays as the solution to my > out-of-tree nightmare nearly 2 years ago... I'm hardly saying you should have done something different. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
