From: Ahmad Fatoum <ahmad@a3f.at>
To: barebox@lists.infradead.org
Subject: [PATCH 2/2] fixup! Documentation: document barebox device tree handling
Date: Tue, 1 Oct 2019 08:28:53 +0200 [thread overview]
Message-ID: <20191001062853.1256-3-ahmad@a3f.at> (raw)
In-Reply-To: <20191001062853.1256-1-ahmad@a3f.at>
---
Documentation/devicetree/index.rst | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/Documentation/devicetree/index.rst b/Documentation/devicetree/index.rst
index 3b911c5a9d42..908652642b9a 100644
--- a/Documentation/devicetree/index.rst
+++ b/Documentation/devicetree/index.rst
@@ -20,7 +20,7 @@ They are located under the top-level ``dts/`` directory.
Patches against ``dts/`` and its subdirectories are not accepted upstream.
-.. _kernel.org device-tree repository: https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasing.git/
+.. _kernel.org Split device-tree repository: https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebasing.git/
barebox Device Trees
--------------------
@@ -34,21 +34,24 @@ environment or boot-time device configuration.
Device Tree Compiler
--------------------
-barebox makes use of the ``dtc`` and ``fdtget`` utilities from the `Device-Tree
-Compiler`_ project.
+barebox makes use of the ``dtc`` and ``fdtget`` and the underlying ``libfdt``
+from the `Device-Tree Compiler`_ project.
.. _Device-Tree Compiler: https://git.kernel.org/pub/scm/utils/dtc/dtc.git
-These utilities are built as part of the barebox build process.
+These utilities are built as part of the barebox build process. Additionally,
+libfdt is compiled once more as part of the ``CONFIG_BOARD_ARM_GENERIC_DT``
+if selected.
-Steps to update ``dtc``:
+Steps to update ``scripts/dtc``:
* Place a ``git-checkout`` of the upstream ``dtc`` directory in the parent
directory of your barebox ``git-checkout``.
* Run ``scripts/dtc/update-dtc-source.sh`` from the top-level barebox directory.
* Wait till ``dtc`` build, test, install and commit conclude.
-* If ``scripts/dtc/Makefile`` changes are necessary, apply them manually in
- a commit preceding the ``dtc`` update.
+* Compile-test with ``CONFIG_BOARD_ARM_GENERIC_DT=y``.
+* If ``scripts/dtc/Makefile`` or barebox include file changes are necessary,
+ apply them manually in a commit preceding the ``dtc`` update.
barebox-specific Bindings
-------------------------
--
2.20.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-10-01 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 6:28 [PATCH 0/2] dtc: fix breakage of in-barebox libfdt Ahmad Fatoum
2019-10-01 6:28 ` [PATCH 1/2] lib: fdt: define INT32_MAX for in-barebox use Ahmad Fatoum
2019-10-01 6:28 ` Ahmad Fatoum [this message]
2019-10-02 6:48 ` [PATCH 0/2] dtc: fix breakage of in-barebox libfdt Sascha Hauer
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=20191001062853.1256-3-ahmad@a3f.at \
--to=ahmad@a3f.at \
--cc=barebox@lists.infradead.org \
/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