On Mon, 2013-10-21 at 11:15 +0200, Thierry Reding wrote: > A stable ABI means there's about zero chance of redesigning something > after it's been merged. Unless we want to live with having to support > several DT bindings in a driver. > That will happen for sure, and it will suffer from lack of testing of "old" bindings, like every uncommon combinations supported by the kernel today (think 32b userspace over 64b kernel). Solution: always use latest DT shipped with kernel. > impossible to take into account every possible detail up front simply > because we're all only human and because some things just might change > over time. I'm fairly sure that Linux wouldn't be where it is today if > we didn't have that flexibility. Also, as you said in another mail, new roadblocks have appeared to reach mainline, you now have to convince DT maintainers that your DT bindings are correct / future proof. IMO this will cause even more un-mainlined SOCs/boards, with the added difficulty to integrate the existing proprietary bindings if someone wants to mainline later. -- Maxime -- 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
