1 '\" te
2 .\" Copyright 1989 AT&T Copyright (c) 2003, Sun Microsystems, Inc. All Rights Reserved
3 .\" Copyright 2012, Joyent, Inc. All Rights Reserved
4 .\" Copyright 2019, Peter tribble.
5 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
6 .\" See the License for the specific language governing permissions and limitations under the License. When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the
7 .\" fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
8 .TH PRTCONF 1M "Jan 21, 2019"
9 .SH NAME
10 prtconf \- print system configuration
11 .SH SYNOPSIS
12 .LP
13 .nf
14 \fB/usr/sbin/prtconf\fR [\fB-V\fR] | [\fB-F\fR] | [\fB-m\fr] | [\fB-x\fR] | [\fB-bpv\fR] | [\fB-acdDPv\fR]
15 [\fIdev_path\fR]
16 .fi
17
18 .SH DESCRIPTION
19 .LP
20 The \fBprtconf\fR command prints the system configuration information. The
21 output includes the total amount of memory, and the configuration of system
22 peripherals formatted as a device tree.
23 .sp
24 .LP
25 If a device path is specified on the command line for those command options
26 that can take a device path, \fBprtconf\fR will only display information for
27 that device node.
28 .SH OPTIONS
29 .LP
30 The following options are supported:
31 .sp
32 .ne 2
33 .na
34 \fB-a\fR
35 .ad
36 .RS 6n
37 Display all the ancestors device nodes, up to the root node of the device tree,
38 for the device specified on the command line.
39 .RE
40
41 .sp
42 .ne 2
43 .na
44 \fB-b\fR
45 .ad
46 .RS 6n
47 Display the firmware device tree root properties for the purpose of platform
48 identification. These properties are "name", "compatible", "banner-name" and
49 "model".
147 Displays platform-dependent \fBPROM\fR (on SPARC platforms) or booting system
148 (on x86 platforms) version information. This flag must be used by itself. The
149 output is a string. The format of the string is arbitrary and
150 platform-dependent.
151 .RE
152
153 .sp
154 .ne 2
155 .na
156 \fB-x\fR
157 .ad
158 .RS 6n
159 A legacy flag that reported if the firmware on this system is 64-bit ready.
160 As illumos only runs on 64-bit platforms, this flag is kept for compatibility
161 only, and zero is always returned.
162 .sp
163 This flag overrides all other flags and must be used by itself.
164 .RE
165
166 .SH OPERANDS
167 .LP
168 The following operands are supported:
169 .sp
170 .ne 2
171 .na
172 \fIdev_path\fR
173 .ad
174 .RS 12n
175 The path to a target device minor node, device nexus node, or device link for
176 which device node configuration information is displayed
177 .RE
178
179 .SH EXIT STATUS
180 .LP
181 The following exit values are returned:
182 .sp
183 .ne 2
184 .na
185 \fB0\fR
186 .ad
187 .RS 12n
188 No error occurred.
189 .RE
190
191 .sp
192 .ne 2
193 .na
194 \fBnon-zero\fR
195 .ad
196 .RS 12n
197 With the \fB-F\fR option, a non-zero return value means that the
198 output device is not a frame buffer. In all other cases, a
199 non-zero return value means that an error occurred.
200 .RE
201
202 .SH ATTRIBUTES
203 .LP
204 See \fBattributes\fR(5) for descriptions of the following attributes:
205 .sp
206
207 .sp
208 .TS
209 box;
210 c | c
211 l | l .
212 ATTRIBUTE TYPE ATTRIBUTE VALUE
213 Interface Stability Unstable
214 .TE
215
216 .SH SEE ALSO
217 .LP
218 \fBfuser\fR(1M), \fBmodinfo\fR(1M), \fBsysdef\fR(1M), \fBattributes\fR(5),
219 \fBopenprom\fR(7D)
220 .SH NOTES
221 .LP
222 The output of the \fBprtconf\fR command is highly dependent on the version of
223 the \fBPROM\fR installed in the system. The output will be affected in
224 potentially all circumstances.
225 .sp
226 .LP
227 The \fBdriver not attached\fR message means that no driver is currently
228 attached to that instance of the device. In general, drivers are loaded and
229 installed (and attached to hardware instances) on demand, and when needed, and
230 may be uninstalled and unloaded when the device is not in use.
231 .sp
232 .LP
233 On x86 platforms, the use of \fBprtconf\fR \fB-vp\fR provides a subset of
234 information from \fBprtconf\fR \fB-v\fR. The value of integer properties from
235 \fBprtconf\fR \fB-vp\fR might require byte swapping for correct interpretation.
|
1 '\" te
2 .\" Copyright 1989 AT&T Copyright (c) 2003, Sun Microsystems, Inc. All Rights Reserved
3 .\" Copyright 2012, Joyent, Inc. All Rights Reserved
4 .\" Copyright 2019, Peter tribble.
5 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
6 .\" See the License for the specific language governing permissions and limitations under the License. When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the
7 .\" fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
8 .TH PRTCONF 1M "Jan 21, 2019"
9 .SH NAME
10 prtconf \- print system configuration
11 .SH SYNOPSIS
12 .nf
13 \fB/usr/sbin/prtconf\fR [\fB-V\fR] | [\fB-F\fR] | [\fB-m\fR] | [\fB-x\fR] | [\fB-bpv\fR] | [\fB-acdDPv\fR]
14 [\fIdev_path\fR]
15 .fi
16
17 .SH DESCRIPTION
18 The \fBprtconf\fR command prints the system configuration information. The
19 output includes the total amount of memory, and the configuration of system
20 peripherals formatted as a device tree.
21 .sp
22 .LP
23 If a device path is specified on the command line for those command options
24 that can take a device path, \fBprtconf\fR will only display information for
25 that device node.
26 .SH OPTIONS
27 The following options are supported:
28 .sp
29 .ne 2
30 .na
31 \fB-a\fR
32 .ad
33 .RS 6n
34 Display all the ancestors device nodes, up to the root node of the device tree,
35 for the device specified on the command line.
36 .RE
37
38 .sp
39 .ne 2
40 .na
41 \fB-b\fR
42 .ad
43 .RS 6n
44 Display the firmware device tree root properties for the purpose of platform
45 identification. These properties are "name", "compatible", "banner-name" and
46 "model".
144 Displays platform-dependent \fBPROM\fR (on SPARC platforms) or booting system
145 (on x86 platforms) version information. This flag must be used by itself. The
146 output is a string. The format of the string is arbitrary and
147 platform-dependent.
148 .RE
149
150 .sp
151 .ne 2
152 .na
153 \fB-x\fR
154 .ad
155 .RS 6n
156 A legacy flag that reported if the firmware on this system is 64-bit ready.
157 As illumos only runs on 64-bit platforms, this flag is kept for compatibility
158 only, and zero is always returned.
159 .sp
160 This flag overrides all other flags and must be used by itself.
161 .RE
162
163 .SH OPERANDS
164 The following operands are supported:
165 .sp
166 .ne 2
167 .na
168 \fIdev_path\fR
169 .ad
170 .RS 12n
171 The path to a target device minor node, device nexus node, or device link for
172 which device node configuration information is displayed
173 .RE
174
175 .SH EXIT STATUS
176 The following exit values are returned:
177 .sp
178 .ne 2
179 .na
180 \fB0\fR
181 .ad
182 .RS 12n
183 No error occurred.
184 .RE
185
186 .sp
187 .ne 2
188 .na
189 \fBnon-zero\fR
190 .ad
191 .RS 12n
192 With the \fB-F\fR option, a non-zero return value means that the
193 output device is not a frame buffer. In all other cases, a
194 non-zero return value means that an error occurred.
195 .RE
196
197 .SH ATTRIBUTES
198 See \fBattributes\fR(5) for descriptions of the following attributes:
199 .sp
200
201 .sp
202 .TS
203 box;
204 c | c
205 l | l .
206 ATTRIBUTE TYPE ATTRIBUTE VALUE
207 Interface Stability Unstable
208 .TE
209
210 .SH SEE ALSO
211 \fBfuser\fR(1M), \fBmodinfo\fR(1M), \fBsysdef\fR(1M), \fBattributes\fR(5),
212 \fBopenprom\fR(7D)
213 .SH NOTES
214 The output of the \fBprtconf\fR command is highly dependent on the version of
215 the \fBPROM\fR installed in the system. The output will be affected in
216 potentially all circumstances.
217 .sp
218 .LP
219 The \fBdriver not attached\fR message means that no driver is currently
220 attached to that instance of the device. In general, drivers are loaded and
221 installed (and attached to hardware instances) on demand, and when needed, and
222 may be uninstalled and unloaded when the device is not in use.
223 .sp
224 .LP
225 On x86 platforms, the use of \fBprtconf\fR \fB-vp\fR provides a subset of
226 information from \fBprtconf\fR \fB-v\fR. The value of integer properties from
227 \fBprtconf\fR \fB-vp\fR might require byte swapping for correct interpretation.
|