On 23 October 2013 11:04, Thierry Reding <thierry.reding@xxxxxxxxx> wrote: > I think there's some broad agreement about what stable bindings entail. > Essentially it means at no point in the future a new kernel is allowed > to stop working with an old binding. > > It also entails that bindings can change, but only in ways that don't > break backwards-compatibility. In my opinion it should also mean that all the same functionality you got with the old kernel remains enabled. In other words, if the old kernel could drive the framebuffer because the framebuffer was still handled by platform data, then you can't break this when you introduce a new dt binding for the framebuffer; you have to cope with "dt blob has no node for this device because it's old". "The kernel boots but it doesn't find half the devices" is just as broken as "the kernel doesn't boot" if you're an end user trying to use the old device tree blob with a new kernel... thanks -- PMM -- 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
