Lines Matching full:will
12 format. As a part of its enterprise class servers, IBM will use the IPZ format
41 the SN keyword will contain a serial number that can uniquely identify an
56 specification does define it, but will need to use the ECC for IBM's
74 Some of the VPD will need to be exchanged with the host.
83 to synthesize VPD for such FRUs. Details on VPD synthesis will be in its own
128 updates will be made:
130 - Two new services will be created to handle the new VPD formats. ipz-vpd-parser
134 - Another service will be created to update the inventory with location code
139 - There will be one udev rule per EEPROM on the system from which the BMC has to
143 - Each udev rule will be setup to launch an instance of one of the VPD parser
148 launched, will read the EEPROM, parse its contents and use config files to
151 - The service will update the inventory D-Bus object with the contents of the
152 VPD in the following format: There will be one interface per record (ex, VINI
153 record) which will have each keyword as a property (ex, FN, PN). This will
154 allow us to support multiple records that can have the same keyword and will
172 - The parser services will not format or transform the data in VPD in any way
174 byte arrays. Note, however, that the services will continue updating the
178 - To handle VPD writes, another systemd service will be launched once all the
179 VPD read services have completed. This service shall be a daemon that will
180 manage parallel writes to EEPROMs. The VPD writer service will expose D-bus
191 when the host is up and running) will be handled. That will be presented in
202 daemon that will expose a set of D-bus interfaces to:
207 - Concurrently maintain a FRU, which will in turn perform a remove/add/replace
252 - The services to parse VPD and store it in the inventory will add some time to
255 - Applications that need to read VPD keywords will be impacted in the sense that
264 mode into the application. The file mode will not need real hardware to test the