Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ioreg(8) [osx man page]

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

ioreg -- show I/O Kit registry SYNOPSIS
ioreg [-abfilrtx] [-c class] [-d depth] [-k key] [-n name] [-p plane] [-w width] DESCRIPTION
ioreg displays the I/O Kit registry. It shows the heirarchical registry structure as an inverted tree. The provider-client relationships among those objects is shown as follows: +-o provider | +-o client By default, object properties are not shown. The use of the -c, -k, -l, or -n options cause ioreg to show properties for objects that match the specified criteria. By supplying the -r option, the user may specify the object which will appear at the root of the tree with the -c, -k, or -n options. If root matches more than one object, multiple trees will be displayed. The options are as follows: -a Archive the output in XML. -b Show the object name in bold. -c Show the object properties only if the object is an instance of, or derives from, the specified C++ class (e.g. IOService). -d Limit tree traversal to the specified depth. The depth limit is applied with respect to each subtree root individually. Therefore, supplying a depth of 1 will cause ioreg to display only (sub)tree root nodes; children will not be shown. -f Enable smart formatting. ioreg knows how to format certain properties so that the output is more readable and meaningful, decoding data fields where appropriate. Currently supported are `reg', `assigned-addresses', `slot-names', `ranges', `interrupt-map', `inter- rupt-parent`, and `interrupts'. -i Show the object inheritance. -k Show the object properties only if the object has the specified key. Substrings do not match; the specified key must be a full prop- erty name. -l Show properties for all displayed objects. -n Show the object properties only if the object has the specified name. The object location, if any, is considered part of the name, thus pci@f0000000 and pci@f4000000 are distinct names. -p Traverse the registry over the specified plane. The default plane value is ``IOService''. The other planes, such as ``IODeviceTree'', can be found under the ``IORegistryPlanes'' property of the root object (ioreg -d 1 -k IORegistryPlanes). -r Show subtrees rooted by objects that match the specified criteria. If none of -c, -k, or -n are supplied, -r has no effect. -t Show tree location of each subtree. This option causes ioreg to display all nodes between the I/O Kit Root and the root of the dis- played subtree, i.e. the subtree's parent, grandparent, etc. -w Clip the output to the specified line width. The default width value is the current screen size. A value of 0 specifies an unlimited line width. -x Show data and numbers as hexadecimal. Darwin September 26, 2011 Darwin

Check Out this Related Man Page

GIT-LS-TREE(1)							    Git Manual							    GIT-LS-TREE(1)

git-ls-tree - List the contents of a tree object SYNOPSIS
git ls-tree [-d] [-r] [-t] [-l] [-z] [--name-only] [--name-status] [--full-name] [--full-tree] [--abbrev[=<n>]] <tree-ish> [<path>...] DESCRIPTION
Lists the contents of a given tree object, like what "/bin/ls -a" does in the current working directory. Note that: o the behaviour is slightly different from that of "/bin/ls" in that the <path> denotes just a list of patterns to match, e.g. so specifying directory name (without -r) will behave differently, and order of the arguments does not matter. o the behaviour is similar to that of "/bin/ls" in that the <path> is taken as relative to the current working directory. E.g. when you are in a directory sub that has a directory dir, you can run git ls-tree -r HEAD dir to list the contents of the tree (that is sub/dir in HEAD). You don't want to give a tree that is not at the root level (e.g. git ls-tree -r HEAD:sub dir) in this case, as that would result in asking for sub/sub/dir in the HEAD commit. However, the current working directory can be ignored by passing --full-tree option. OPTIONS
<tree-ish> Id of a tree-ish. -d Show only the named tree entry itself, not its children. -r Recurse into sub-trees. -t Show tree entries even when going to recurse them. Has no effect if -r was not passed. -d implies -t. -l, --long Show object size of blob (file) entries. -z line termination on output. --name-only, --name-status List only filenames (instead of the "long" output), one per line. --abbrev[=<n>] Instead of showing the full 40-byte hexadecimal object lines, show only a partial prefix. Non default number of digits can be specified with --abbrev=<n>. --full-name Instead of showing the path names relative to the current working directory, show the full path names. --full-tree Do not limit the listing to the current working directory. Implies --full-name. [<path>...] When paths are given, show them (note that this isn't really raw pathnames, but rather a list of patterns to match). Otherwise implicitly uses the root level of the tree as the sole path argument. OUTPUT FORMAT
<mode> SP <type> SP <object> TAB <file> Unless the -z option is used, TAB, LF, and backslash characters in pathnames are represented as , , and \, respectively. This output format is compatible with what --index-info --stdin of git update-index expects. When the -l option is used, format changes to <mode> SP <type> SP <object> SP <object size> TAB <file> Object size identified by <object> is given in bytes, and right-justified with minimum width of 7 characters. Object size is given only for blobs (file) entries; for other entries - character is used in place of size. GIT
Part of the git(1) suite Git 01/14/2014 GIT-LS-TREE(1)
Man Page