openslx-ng/ipxe.git/src/interface/smbios, branch master

[settings] Expose SMBIOS settings as global variables

2015-12-23T15:29:55+00:00

Signed-off-by: Michael Brown

[legal] Relicense files under GPL2_OR_LATER_OR_UBDL

2015-03-02T16:35:29+00:00

These files cannot be automatically relicensed by util/relicense.pl since they either contain unusual but trivial contributions (such as the addition of __nonnull function attributes), or contain lines dating back to the initial git revision (and so require manual knowledge of the code's origin). Signed-off-by: Michael Brown

[legal] Relicense files under GPL2_OR_LATER_OR_UBDL

2015-03-02T14:17:31+00:00

Relicense files for which I am the sole author (as identified by util/relicense.pl). Signed-off-by: Michael Brown

[smbios] Expose board serial number as ${board-serial}

2014-06-12T16:59:52+00:00

With blade servers, the chassis serial number (exposed via ${serial}) may not be unique. Expose ${board-serial} as a named setting to provide easy access to a more meaningful serial number. Signed-off-by: Michael Brown

[settings] Force settings into alphabetical order within sections

2013-12-05T12:43:28+00:00

Signed-off-by: Michael Brown

[linux] Provide access to SMBIOS via /dev/mem

2013-12-05T03:16:27+00:00

Signed-off-by: Michael Brown

[settings] Explicitly separate the concept of a completed fetched setting

2013-12-05T00:37:02+00:00

The fetch_setting() family of functions may currently modify the definition of the specified setting (e.g. to add missing type information). Clean up this interface by requiring callers to provide an explicit buffer to contain the completed definition of the fetched setting, if required. Signed-off-by: Michael Brown

[settings] Clarify usage of the term "named setting"

2013-07-18T14:50:02+00:00

There are currently two conflicting usages of the term "named setting" within iPXE: one refers to predefined settings (such as show up in the "config" UI), the other refers to settings identified by a name (such as "net0.dhcp/ip"). Split these usages into the term "predefined setting" and "named setting" to avoid ambiguity. Signed-off-by: Michael Brown

[smbios] Allow access to multiple instances of SMBIOS structures

2013-05-01T21:11:04+00:00

Extend the syntax for numerical SMBIOS settings from smbios/.. to smbios/[.].. Where SMBIOS provides multiple structures with the same , this extended syntax allows for access to structures other than the first. If is omitted then it will default to zero, giving access to the first instance (and so matching existing behaviour). The 16-bit SMBIOS handle (which is an alternative way to disambiguate multiple instances of the same type of structure) can be accessed, if required, using smbios/..2.2:uint16 Signed-off-by: Michael Brown

[smbios] Allow access to unreferenced SMBIOS strings

2013-05-01T21:11:04+00:00

iPXE allows access to general SMBIOS settings using the syntax: smbios/.. This provides access to any fixed-offset field within an SMBIOS structure. This syntax is currently overloaded to interpret a zero as meaning that the byte at contains a string index; this provides access to SMBIOS strings (which are not located at fixed offsets). The "OEM Strings" SMBIOS structure contains strings which are not referenced by any fixed string index field within the structure. iPXE currently provides no way to access these strings. Fix by overloading the syntax for numerical SMBIOS settings to interpret an of zero as implying that contains a literal string index. The OEM Strings can then be accessed using: smbios/11.0.1 smbios/11.0.2 smbios/11.0.3 ... The actual byte at offset zero will always contain the structure type, which is already known since it must be specified in order to access the structure. There is thus no plausible existing use case for an offset of zero; overloading the syntax in this way should therefore not break compatibility with any existing scripts. The corner case where both and are zero is undefined (and, for now, will simply return a "not found" error). Signed-off-by: Michael Brown