<title>sysconf UI command design: for Flexible Device Configuration
</title>
<body bgcolor=
"#FFFFFF" LANG=
"en-US">
<h1> SAM sysconf UI command for flexible device configuration
</h1>
This document describes sysconf UI command syntax and introduces the example
use of the command for creating a device hierarchy that similate a hardware
<li> SAM: SPARC Architecture Model
<br>
<li> Module Model Interface (MMI)
<br>
<li>SAM Flexible Configuration
<br>
<h2>sysconf UI command
</h2>
<ul><tt><b>sysconf
[ -p mod_path ] module_name
[ instance_name
[ args ... ] [ -d# ] ]
</b></tt></ul>
<ul><tt>cfg
</tt> is an alias for
<tt>sysconf
</tt>.
</ul>
<tr><td><i>mod_path
</i></td> <td> pathname for .so files
</td></tr>
<tr><td><i>module_name
</i></td> <td> a module name defined by MMI
</td></tr>
<tr><td><i>instance_name
</i></td> <td> a unique instance name
</td></tr>
<tr><td><i>args
</i></td> <td> optional arguments, usually
<b>name=value
</b> pairs.
</td></tr>
<tr><td><i>-d#
</i></td> <td> set debug level to control the amount of debug output
</td></tr>
The .so filename is contructed as follows:
<i>mod_path
</i>/
<i>module_name
</i>.so.
The default value for
<i>mod_path
</i> is
".".
The
<i>-p
</i> switch sets a new module path, and remains in effect until the next
<i>-p
</i> switch.
Example device hierarchy:
Example sysconf commands for above device hierarchy:
sysconf -p ../blaze-conf/modules/
64opt
sysconf schizo schizo30 aid=
30 pciA=pci30A pciB=pci30B
sysconf pci_bus pci30A bridge=schizo30
sysconf fc fc0 bus=pci30A dev=
0 fun=
0
sysconf isa isa0 bus=pci30A dev=
7 fun=
0
sysconf pci_bus pci30B bridge=schizo30
sysconf bootbus bootbus_ctrl bus=pci30B dev=
4 fun=
0
sysconf schizo schizo31 aid=
31 pciA=pci31A pciB=pci31B
sysconf pci_bus pci31A bridge=schizo31
sysconf ge ge0 bus=pci31A dev=
0 fun=
0
sysconf ge ge1 bus=pci31A dev=
1 fun=
0
sysconf pci_bus pci31B bridge=schizo31