You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: common/v1/autogen.md
+49-32Lines changed: 49 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,14 +36,14 @@
36
36
<aname="opi_api-inventory-v1-BIOSInfo"></a>
37
37
38
38
### BIOSInfo
39
-
39
+
BIOS Information (Type 0)
40
40
41
41
42
42
| Field | Type | Label | Description |
43
43
| ----- | ---- | ----- | ----------- |
44
-
| vendor |[string](#string)|||
45
-
| version |[string](#string)|||
46
-
| date |[string](#string)|||
44
+
| vendor |[string](#string)||String number of the BIOS Vendor’s Name.|
45
+
| version |[string](#string)||String number of the BIOS Version. This value is a free-form string that may contain Core and OEM version information.|
46
+
| date |[string](#string)||String number of the BIOS release date. The date string, if supplied, is in either mm/dd/yy or mm/dd/yyyy format. If the year portion of the string is two digits, the year is assumed to be 19yy. NOTE: The mm/dd/yyyy format is required for SMBIOS version 2.3 and later|
47
47
48
48
49
49
@@ -53,16 +53,18 @@
53
53
<aname="opi_api-inventory-v1-BaseboardInfo"></a>
54
54
55
55
### BaseboardInfo
56
-
56
+
Baseboard (or Module) Information (Type 2)
57
+
The information in this structure defines attributes of a system baseboard (for
58
+
example, a motherboard, planar, server blade, or other standard system module)
57
59
58
60
59
61
| Field | Type | Label | Description |
60
62
| ----- | ---- | ----- | ----------- |
61
-
| asset_tag |[string](#string)|||
62
-
| serial_number |[string](#string)|||
63
-
| vendor |[string](#string)|||
64
-
| version |[string](#string)|||
65
-
| product |[string](#string)|||
63
+
| asset_tag |[string](#string)||Number of a null-terminated string|
64
+
| serial_number |[string](#string)||Number of null-terminated string|
65
+
| vendor |[string](#string)||Number of null-terminated string|
66
+
| version |[string](#string)||Number of null-terminated string|
67
+
| product |[string](#string)||Number of null-terminated string|
66
68
67
69
68
70
@@ -72,13 +74,17 @@
72
74
<aname="opi_api-inventory-v1-CPUInfo"></a>
73
75
74
76
### CPUInfo
75
-
77
+
Processor Information (Type 4)
78
+
The information in this structure (see Table 21) defines the attributes of a single processor; a separate
79
+
structure instance is provided for each system processor socket/slot. For example, a system with an
80
+
IntelDX2™ processor would have a single structure instance while a system with an IntelSX2™ processor
81
+
would have a structure to describe the main CPU and a second structure to describe the 80487 co1054 processor.
76
82
77
83
78
84
| Field | Type | Label | Description |
79
85
| ----- | ---- | ----- | ----------- |
80
-
| total_cores |[int32](#int32)|||
81
-
| total_threads |[int32](#int32)|||
86
+
| total_cores |[int32](#int32)||Number of cores per processor socket See 7.5.6. If the value is unknown, the field is set to 0. For core counts of 256 or greater, the Core Count field is set to FFh and the Core Count 2 field is set to the number of cores.|
87
+
| total_threads |[int32](#int32)||Number of threads per processor socket See 7.5.8. If the value is unknown, the field is set to 0. For thread counts of 256 or greater, the Thread Count field is set to FFh and the Thread Count 2 field is set to the number of threads.|
82
88
83
89
84
90
@@ -88,17 +94,22 @@
88
94
<aname="opi_api-inventory-v1-ChassisInfo"></a>
89
95
90
96
### ChassisInfo
91
-
97
+
System Enclosure or Chassis (Type 3)
98
+
The information in this structure (see Table 16) defines attributes of the system’s mechanical
99
+
enclosure(s). For example, if a system included a separate enclosure for its peripheral devices, two
100
+
structures would be returned: one for the main system enclosure and the second for the peripheral device
101
+
enclosure. The additions to this structure in version 2.1 of this specification support the population of the
102
+
CIM_Chassis class.
92
103
93
104
94
105
| Field | Type | Label | Description |
95
106
| ----- | ---- | ----- | ----------- |
96
-
| asset_tag |[string](#string)|||
97
-
| serial_number |[string](#string)|||
98
-
| type |[string](#string)|||
99
-
| type_description |[string](#string)|||
100
-
| vendor |[string](#string)|||
101
-
| version |[string](#string)|||
107
+
| asset_tag |[string](#string)||Number of null-terminated string|
108
+
| serial_number |[string](#string)||Number of null-terminated string|
109
+
| type |[string](#string)||Bit 7 Chassis lock is present if 1. Otherwise, either a lock is not present, or it is unknown if the enclosure has a lock. Bits 6:0 Enumeration value; see below.|
110
+
| type_description |[string](#string)||Table 17 shows the byte values for the System Enclosure or Chassis Types field Number of null-terminated string|
111
+
| vendor |[string](#string)||Number of null-terminated string|
112
+
| version |[string](#string)||Number of null-terminated string|
102
113
103
114
104
115
@@ -108,7 +119,7 @@
108
119
<aname="opi_api-inventory-v1-DeviceInfo"></a>
109
120
110
121
### DeviceInfo
111
-
122
+
TODO: remove this message
112
123
113
124
114
125
| Field | Type | Label | Description |
@@ -163,13 +174,15 @@ Empty
163
174
<aname="opi_api-inventory-v1-MemoryInfo"></a>
164
175
165
176
### MemoryInfo
166
-
177
+
Physical Memory Array (Type 16)
178
+
This structure describes a collection of memory devices that operate together to form a memory address
179
+
space.
167
180
168
181
169
182
| Field | Type | Label | Description |
170
183
| ----- | ---- | ----- | ----------- |
171
-
| total_physical_bytes |[int64](#int64)|||
172
-
| total_usable_bytes |[int64](#int64)|||
184
+
| total_physical_bytes |[int64](#int64)||Maximum memory capacity, in kilobytes, for this array If the capacity is not represented in this field, then this field contains 8000 0000h and the Extended Maximum Capacity field should be used. Values 2 TB (8000 0000h) or greater must be represented in the Extended Maximum Capacity field.|
185
+
| total_usable_bytes |[int64](#int64)||TBD|
173
186
174
187
175
188
@@ -179,18 +192,22 @@ Empty
179
192
<aname="opi_api-inventory-v1-SystemInfo"></a>
180
193
181
194
### SystemInfo
182
-
195
+
System Information (Type 1)
196
+
The information in this structure defines attributes of the overall system and is intended to be associated
197
+
with the Component ID group of the system’s MIF. An SMBIOS implementation is associated with a single
198
+
system instance and contains one and only one System Information (Type 1) structure. Table 10 shows
199
+
the contents of this structure.
183
200
184
201
185
202
| Field | Type | Label | Description |
186
203
| ----- | ---- | ----- | ----------- |
187
-
| family |[string](#string)|||
188
-
| name |[string](#string)|||
189
-
| vendor |[string](#string)|||
190
-
| serial_number |[string](#string)|||
191
-
| uuid |[string](#string)|||
192
-
| sku |[string](#string)|||
193
-
| version |[string](#string)|||
204
+
| family |[string](#string)||Number of null-terminated string This text string identifies the family to which a particular computer belongs. A family refers to a set of computers that are similar but not identical from a hardware or software point of view. Typically, a family is composed of different computer models, which have different configurations and pricing points. Computers in the same family often have similar branding and cosmetic features.|
205
+
| name |[string](#string)||Number of null-terminated string|
206
+
| vendor |[string](#string)||Number of null-terminated string|
207
+
| serial_number |[string](#string)||Number of null-terminated string|
208
+
| uuid |[string](#string)||A UUID is an identifier that is designed to be unique across both time and space. It requires no central registration process. The UUID is 128 bits long. Its format is described in RFC4122, but the actual field contents are opaque and not significant to the SMBIOS specification, which is only concerned with the byte order. Table 11 shows the field names; these field names, particularly for multiplexed fields, follow historical practice.|
209
+
| sku |[string](#string)||Number of null-terminated string This text string identifies a particular computer configuration for sale. It is sometimes also called a product ID or purchase order number. This number is frequently found in existing fields, but there is no standard format. Typically for a given system board from a given OEM, there are tens of unique processor, memory, hard drive, and optical drive configurations.|
210
+
| version |[string](#string)||Number of null-terminated string|
0 commit comments