Mon, 5 May 2014 10:20:49 +0200 от Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>: > Some updates how I intend to handle upstream dts changes in barebox. > > - I will merge the latest upstream dts changes to barebox for each Linux > rc. Should dts changes introduce regressions this will at least give us > the Linux rc which introduced it > - I will always merge dts updates to barebox next, not to master. While > dts changes may be needed in master to fix regressions on one board, > they could also introduce new regressions on other boards. Should we > need dts changes to fix regressions in barebox master, we have to do > it using overlays in arch/*/dts/ until an upstream fix arrives in dts/ > - I will not send the dts updates to the list, I'll just merge them to > barebox next some time after a new Linux rc arrived (As just happened > with 3.15-rc3) Just to understand our further concept: (I will use the example based on i.MX25). We have 3 files in the arch/arm/dts/imx25*. Should we now remove all of them, create our overlay for karo-tx25 board and include basic file <arm/imx25-karo-tx25.dts> in the top of new overlay file as basic DTS? --- _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
