From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] README: Device Tree: Add & explain undocumented options.
Date: Fri, 24 Jun 2016 16:47:01 -0400 [thread overview]
Message-ID: <20160624204701.GE19080@bill-the-cat> (raw)
In-Reply-To: <1465649802-7425-1-git-send-email-engkhalil86@gmail.com>
On Sat, Jun 11, 2016 at 02:56:42PM +0200, Ahmed Samir Khalil wrote:
> There are no info about these options in the README.
> Documenting these options makes getting startup,
> configuration & testing easier.
>
> Signed-off-by: Ahmed Samir Khalil <engkhalil86@gmail.com>
> ---
> README | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/README b/README
> index 1d0b946..1c9f778 100644
> --- a/README
> +++ b/README
> @@ -1154,6 +1154,14 @@ The following options need to be configured:
> still use the individual files if you need something more
> exotic.
>
> + CONFIG_OF_HOSTFILE
> + If this variable is defined, U-Boot will read the device tree
> + from a file on startup. This is only useful for sandbox. You
> + may use either CONFIG_OF_HOSTFILE or CONFIG_OF_CONTROL.
> +
> + CONFIG_OF_SPI_FLASH
> + Define to enable setting up a new SPI flash (slave) from an fdt node.
I'm not sure if OF_SPI_FLASH works even as nothing calls it today. Can
you please just do a patch that documents CONFIG_OF_HOSTFILE? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160624/2449767c/attachment.sig>
prev parent reply other threads:[~2016-06-24 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 12:56 [U-Boot] [PATCH] README: Device Tree: Add & explain undocumented options Ahmed Samir Khalil
2016-06-24 20:47 ` Tom Rini [this message]
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=20160624204701.GE19080@bill-the-cat \
--to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox