summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorJohn Klug <john.klug@multitech.com>2020-09-17 17:14:44 -0500
committerJohn Klug <john.klug@multitech.com>2020-09-17 17:14:44 -0500
commit8e4259ba2bdfe210e9963a58c3924e4a0ad49377 (patch)
treebad3656049c538a53bda9d14782dcd4825c16c2a /README
parent9f386f6f88c822a9a1f6ea7188c5a14ab6bb609a (diff)
downloadmt-dt-overlay-8e4259ba2bdfe210e9963a58c3924e4a0ad49377.tar.gz
mt-dt-overlay-8e4259ba2bdfe210e9963a58c3924e4a0ad49377.tar.bz2
mt-dt-overlay-8e4259ba2bdfe210e9963a58c3924e4a0ad49377.zip
Add file location to dtso file and add uart0 to overlay for MTCAP
Diffstat (limited to 'README')
-rw-r--r--README25
1 files changed, 22 insertions, 3 deletions
diff --git a/README b/README
index 1a4debd..6167976 100644
--- a/README
+++ b/README
@@ -11,9 +11,6 @@ See this for the format of an overlay:
https://www.kernel.org/doc/Documentation/devicetree/overlay-notes.txt
-Note that as of 10 May 2019, no overlays have been
-released.
-
The biggest flaw in overlays, is the inablitiy to use
the phandle described in an alias in the boot
time device tree in an overlay, so it appears
@@ -23,3 +20,25 @@ is common to reference a "pio" in device tree to
use a PIO with GPIO. For example, it does not appear
to be possible to use &pioC in the overlay without
redefining it.
+
+The recipe that uses the overlay reads a comment
+in the overlay source to determine the destination
+and any symlink locations.
+
+The comment in the file must be as follows for
+locations and symlinks:
+
+/*
+ * Put: /a/b/c/d.dtbo
+ * Link: /a/x/y/d.dtbo
+ *
+ */
+
+The install is looking for a line that
+starts with " * Put: " or " * Link: ".
+Extra spaces before the path are allowed.
+The link will always point at the path
+specified by Put.
+
+The path given is relative to the device
+tree overlay location.