Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dtc(1) [debian man page]

DTC(1)							      General Commands Manual							    DTC(1)

NAME
dtc - Device Tree Compiler SYNOPSIS
/usr/bin/dtc [options] <input file> DESCRIPTION
Device Tree Compiler, dtc, takes as input a device-tree in a given format and outputs a device-tree in another format for booting kernels on embedded systems. Typically, the input format is "dts", a human readable source format, and creates a "dtb", or binary format as out- put. OPTIONS
-h Display help text. -q Quiet: -q - Suppress warnings. -qq - Suppress errors. -qqq - Suppress all. -I <input format> Input formats are: dts - device tree source text dtb - device tree blob fs - /proc/device-tree style directory -o <output file> Dump the result into a file, instead of stdout. -O <output format> Output formats are: dts - device tree source text dtb - device tree blob asm - assembler source -V <output version> Blob version to produce. The default is 17 (only relevant for dtb and asm output). -d <output dependency file> -R <number> Make space for <number> reserve map entries (only relevant for dtb and asm output). -S <bytes> Make the blob at least <bytes> long (extra space). -p <bytes> Add padding to the blob of <bytes> long (extra space) -b <number> Set the physical boot CPU. -f Force - try to produce output even if the input tree has errors. -s Sort nodes and properties before outputting (only useful for comparing trees) -v Print DTC version and exit. -H <phandle format> phandle formats are: legacy - "linux,phandle" properties only epapr - "phandle" properties only both - Both "linux,phandle" and "phandle" properties AUTHOR
dtc was written by David Gibson <david@gibson.dropbear.id.au>. Since April 1, 2006, Jon Loeliger <jdl@jdl.com> assumes maintainership. This manual page was originally written by Aurelien GEROME <ag@roxor.cx>, for the Debian project (but may be used by others). This manual page is currently maintained and update it by Hector Oron <zumbi@debian.org>, for the Debian project. Linux 30 January 2012 DTC(1)

Check Out this Related Man Page

DRVCTL(8)						    BSD System Manager's Manual 						 DRVCTL(8)

NAME
drvctl -- tool to rescan busses and detach devices on user request SYNOPSIS
drvctl -r [-a attribute] busdevice [locator ...] drvctl -d device drvctl [-nt] -l [device] drvctl [-n] -p device [property ...] drvctl -Q device drvctl -R device drvctl -S device DESCRIPTION
The drvctl program works with the drvctl(4) pseudo-driver, and allows to rescan busses and to detach drivers from devices. The following options are available: -a Give the interface attribute where children are to be attached to (and which defines the interpretation of the locator information). This will only be needed in rare cases where the bus has multiple attributes. If there are multiple attributes, and one is not spec- ified, drvctl will return an Invalid argument. In such cases, the -p option can be used to determine the available interface attributes. -d Detach the device driver from the device given by the device argument. -l List the children of the device specified by the device argument. If device is not specified, list roots of the device tree instead. Output comes in two columns. The first column is device, or ``root'' if device is not specified. The second column is the child. -n Suppress first column in -l output. Suppress non-XML headers in -p output. -p Get properties for the device specified by the device argument. If property is specified, the value of that property is printed, otherwise the properties are displayed as an XML property list. -Q Resume the ancestors of device, device itself, and all of its descendants. -R Resume both the ancestors of device and device itself. -r Rescan the bus given by the busdevice argument. The scan range can be restricted by an optional locator list. -S Suspend both the descendants of device and device itself. -t Print a tree of devices in -l output. FILES
/dev/drvctl SEE ALSO
proplib(3), autoconf(9) BUGS
Currently, there is no good way to get information about locator lengths and default values (which is present at kernel configuration time) out of a running kernel. Thus the locator handling is less intelligent than it could be. BSD
January 16, 2012 BSD
Man Page

Featured Tech Videos