2005-10-21 09:28:42 +02:00
|
|
|
*.o
|
|
|
|
|
*.d
|
2007-06-14 07:05:55 +02:00
|
|
|
*.a
|
2013-01-21 21:59:17 +01:00
|
|
|
*.patch
|
2007-06-14 07:05:55 +02:00
|
|
|
*.so
|
|
|
|
|
*~
|
2020-03-04 06:05:31 +01:00
|
|
|
*.bak
|
2005-10-21 09:28:42 +02:00
|
|
|
*.tab.[ch]
|
|
|
|
|
lex.yy.c
|
2010-02-24 20:06:23 +01:00
|
|
|
*.lex.c
|
2021-02-03 10:56:36 +01:00
|
|
|
.*.swp
|
2010-02-24 20:06:23 +01:00
|
|
|
/dtc
|
2011-10-25 23:29:24 +02:00
|
|
|
/fdtdump
|
2010-02-24 20:06:23 +01:00
|
|
|
/convert-dtsv0
|
|
|
|
|
/version_gen.h
|
Add fdtget utility to read property values from a device tree
This simply utility makes it easy for scripts to read values from the device
tree. It is written in C and uses the same libfdt as the rest of the dtc
package.
What is it for:
- Reading fdt values from scripts
- Extracting fdt information within build systems
- Looking at particular values without having to dump the entire tree
To use it, specify the fdt binary file on command line followed by a list of
node, property pairs. The utility then looks up each node, finds the property
and displays the value.
Each value is printed on a new line.
fdtget tries to guess the type of each property based on its contents. This
is not always reliable, so you can use the -t option to force fdtget to decode
the value as a string, or byte, etc.
To read from stdin, use - as the file.
Usage:
fdtget <options> <dt file> [<node> <property>]...
Options:
-t <type> Type of data
-h Print this help
<type> s=string, i=int, u=unsigned, x=hex
Optional modifier prefix:
hh or b=byte, h=2 byte, l=4 byte (default)
Signed-off-by: Simon Glass <sjg@chromium.org>
2012-01-21 19:14:47 +01:00
|
|
|
/fdtget
|
Add fdtput utility to write property values to a device tree
This simple utility allows writing of values into a device tree from the
command line. It aimes to be the opposite of fdtget.
What is it for:
- Updating fdt values when a binary blob already exists
(even though source may be available it might be easier to use this
utility rather than sed, etc.)
- Writing machine-specific fdt values within a build system
To use it, specify the fdt binary file on command line followed by the node
and property to set. Then, provide a list of values to put into that
property. Often there will be just one, but fdtput also supports arrays and
string lists.
fdtput does not try to guess the type of the property based on looking at
the arguments. Instead it always assumes that an integer is provided. To
indicate that you want to write a string, use -ts. You can also provide
hex values with -tx.
The command line arguments are joined together into a single value. For
strings, a nul terminator is placed between each string when it is packed
into the property. To avoid this, pass the string as a single argument.
Usage:
fdtput <options> <dt file> <<node> <property> [<value>...]
Options:
-t <type> Type of data
-v Verbose: display each value decoded from command line
-h Print this help
<type> s=string, i=int, u=unsigned, x=hex
Optional modifier prefix:
hh or b=byte, h=2 byte, l=4 byte (default)
To read from stdin and write to stdout, use - as the file. So you can do:
cat somefile.dtb | fdtput -ts - /node prop "My string value" > newfile.dtb
This commit also adds basic tests to verify the major features.
Signed-off-by: Simon Glass <sjg@chromium.org>
2012-01-21 19:14:48 +01:00
|
|
|
/fdtput
|
2017-09-27 11:54:33 +02:00
|
|
|
/fdtoverlay
|
2012-02-03 06:12:01 +01:00
|
|
|
/patches
|
|
|
|
|
/.pc
|
2021-02-03 08:44:22 +01:00
|
|
|
|
|
|
|
|
# cscope files
|
|
|
|
|
cscope.*
|
|
|
|
|
ncscope.*
|
2021-11-11 02:11:35 +01:00
|
|
|
|
|
|
|
|
.eggs/
|
|
|
|
|
build/
|
|
|
|
|
dist/
|
