Hi Maxime, On 27 May 2016 at 03:13, Maxime Ripard <maxime.ripard@xxxxxxxxxxxxxxxxxx> wrote: > The device tree overlays are a good way to deal with user-modifyable nit: modifiable > boards or boards with some kind of an expansion mechanism where we can > easily plug new board in (like the BBB or the raspberry pi). > > However, so far, the usual mechanism to deal with it was to have in Linux > some driver detecting the expansion boards plugged in and then request > these overlays using the firmware interface. > > That works in most cases, but in some cases, you might want to have the > overlays applied before the userspace comes in. Either because the new > board requires some kind of an early initialization, or because your root > filesystem is accessed through that expansion board. > > The easiest solution in such a case is to simply have the component before > Linux applying that overlay, removing all these drawbacks. > > Signed-off-by: Maxime Ripard <maxime.ripard@xxxxxxxxxxxxxxxxxx> > --- > cmd/fdt.c | 20 ++++++++++++++++++++ > 1 file changed, 20 insertions(+) Acked-by: Simon Glass <sjg@xxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe devicetree-compiler" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
