On Tue, Jan 08, 2019 at 04:17:42PM +0200, Andy Shevchenko wrote: > CONFIG_OF_SEPARATE description is not in align with actual code in Makefile > and > thus has misleading instructions and explanation. > > Make it aligned with the actual code.
Bin, is it possible to see this for the next release? > > Signed-off-by: Andy Shevchenko <andriy.shevche...@linux.intel.com> > --- > doc/README.fdt-control | 7 ++++--- > 1 file changed, 4 insertions(+), 3 deletions(-) > > diff --git a/doc/README.fdt-control b/doc/README.fdt-control > index 446401c9e9..e53cf51875 100644 > --- a/doc/README.fdt-control > +++ b/doc/README.fdt-control > @@ -122,13 +122,14 @@ the U-Boot image (including u-boot.bin). This is > suitable for debugging > and development only and is not recommended for production devices. > > If CONFIG_OF_SEPARATE is defined, then it will be built and placed in > -a u-boot.dtb file alongside u-boot.bin. A common approach is then to > +a u-boot.dtb file alongside u-boot-nodtb.bin. A common approach is then to > join the two: > > - cat u-boot.bin u-boot.dtb >image.bin > + cat u-boot-nodtb.bin u-boot.dtb >image.bin > > and then flash image.bin onto your board. Note that U-Boot creates > -u-boot-dtb.bin which does the above step for you also. If you are using > +u-boot-dtb.bin which does the above step for you also. Resulting > +u-boot.bin is a copy of u-boot-dtb.bin in this case. If you are using > CONFIG_SPL_FRAMEWORK, then u-boot.img will be built to include the device > tree binary. > > -- > 2.19.2 > -- With Best Regards, Andy Shevchenko _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot