All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 1/2] doc: Fix CONFIG_OF_SEPARATE description
Date: Wed, 30 Jan 2019 21:54:14 +0200	[thread overview]
Message-ID: <20190130195414.GR9224@smile.fi.intel.com> (raw)
In-Reply-To: <20190108141743.20855-1-andriy.shevchenko@linux.intel.com>

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.shevchenko@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

  parent reply	other threads:[~2019-01-30 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 14:17 [U-Boot] [PATCH v1 1/2] doc: Fix CONFIG_OF_SEPARATE description Andy Shevchenko
2019-01-08 14:17 ` [U-Boot] [PATCH v1 2/2] x86: edison: Switch to CONFIG_OF_SEPARATE Andy Shevchenko
2019-01-10 10:14   ` Ferry Toth
2019-01-10 12:57   ` Simon Glass
2019-01-10 21:48   ` Ferry Toth
2019-01-31  7:38     ` Bin Meng
2019-01-10 12:56 ` [U-Boot] [PATCH v1 1/2] doc: Fix CONFIG_OF_SEPARATE description Simon Glass
2019-01-30 19:54 ` Andy Shevchenko [this message]
2019-01-31  7:38   ` Bin Meng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190130195414.GR9224@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.