summaryrefslogtreecommitdiffstats
path: root/bmc/test
Commit message (Collapse)AuthorAgeFilesLines
* bmc: allowing packing transport flags denselyBenjamin Fair2019-11-1810-42/+16
| | | | | | | | Future transport backends can densely fill in the upper 5 bits of the transport flag bitfield. Signed-off-by: Benjamin Fair <benjaminfair@google.com> Change-Id: Ie4ee59e0581e458a9020775e18270100f9a1de4e
* bmc: add test for reserved flagsBenjamin Fair2019-11-182-0/+67
| | | | | | | | | | Test that no one adds transport backends which use the lower 3 bits of the transport flag bitfield. These bits are reserved for exclusive use with the IPMI, LPC, and P2A backends to ensure backwards compatibility with older host tools. Signed-off-by: Benjamin Fair <benjaminfair@google.com> Change-Id: I6284f2c864aeb5e20a812c0b13e9ecc61349b127
* bmc: require at least one action pack configurationPatrick Venture2019-11-073-52/+56
| | | | | | | | | | | | | | | | In the event the phosphor-ipmi-flash package is added to an image with only a default configuration, it should not register itself as a blob handler. The default installation does not include any json configuration files. Therefore, this lack of a configuration can be checked at load time. Added validation that the firmware image list contains at least two handlers, and one is always the hash blob handler. Added validation that the action map contains at least one action pack configuration. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I0b2f6cded78121869e8a01290d29e420c555a16d
* bmc: merge update and prepare systemdPatrick Venture2019-08-211-5/+2
| | | | | | | | | The update systemd and prepare systemd were effectively the same, and this makes the systemd action generic. Tested: Not tested beyond unit-tests continuing to pass. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I8070731e53bfd6cdafb1d74d9db652f20341985e
* bmc: require blob ids to start with /flash/Patrick Venture2019-08-151-0/+62
| | | | | Signed-off-by: Patrick Venture <venture@google.com> Change-Id: Ib6a0db91d4e2ecd7e7cc3c51ddc1953d9fd8da3c
* bmc: cleanup verification language and symbolsPatrick Venture2019-08-061-1/+1
| | | | | Signed-off-by: Patrick Venture <venture@google.com> Change-Id: Ife4d7e519e44aff60441c5909346ca6d7e2aa090
* bmc: s/SystemdVerification/SystemdWithStatusFile/gPatrick Venture2019-08-051-4/+4
| | | | | Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I5da0ca9e3ae53df957647b19446df4196248fd31
* bmc: allow update to use systemd with pathPatrick Venture2019-08-051-0/+45
| | | | | | | | | Verification provides a mechanism that has a systemd unit and mode, and also a path to check the result. This object can be used for updates, and will be renamed in a later patchset to be more generically named. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I0a995af0aefff76592247775f22fc84189d14903
* bmc: add mode json option for verification systemdPatrick Venture2019-08-051-2/+6
| | | | | Signed-off-by: Patrick Venture <venture@google.com> Change-Id: Ibe5764c4e2ad7dd938177c813c8c6706886258a2
* bmc: move verify systemd mode to parameterPatrick Venture2019-08-051-0/+4
| | | | | | | | | Move the mode for the trigger service to a parameter instead of hard-coding it. This isn't yet a json configuration option, that'll be next. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I59564320015c22be1ec3a4701479d0ee93b9f1f7
* bmc: json configuration: update: add mode parameterPatrick Venture2019-08-051-0/+44
| | | | | | | | | Add the mode parameter as an optional configuration option for the update systemd approach. Previously this was hard-coded as "replace" but now the user can specify something else. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I2bcb61bd9ac5733df6da70f901516d26bd31e2a9
* bmc: move from data section objs to ownedPatrick Venture2019-07-1915-102/+188
| | | | | | | | Move from objects created ahead of purpose to owned objects. This is a step towards integrating with the json support. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I738a5edd40724f17245911af1080c350f029fef1
* bmc: provide disabled json supportPatrick Venture2019-07-182-1/+434
| | | | | | | | Provide support such that a json configuration file can define a firmware handler and its behavior. This is not yet enabled. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: If21f4e97951b3bb91a8afc53bee493d8600a04b7
* build: add option --enable-host-biosPatrick Venture2019-07-031-8/+6
| | | | | | | Add option to enable building in support for the host bios. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I324fc071f07cd364fd39c7df1ccfd9f0fd509a46
* bmc: add ActionPack notion to bundle actionsPatrick Venture2019-07-0312-30/+241
| | | | | | | | Each firmware type will provide its own set of action implementations for each step, preparation, verification, and update. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: Id6409ac356a74e9094272b37709861e2a33d9862
* bmc: only add verifyBlobId if data sent for imagePatrick Venture2019-07-032-2/+12
| | | | | | | | If data was sent to the hash only, don't add verify until they've at least opened the image blob id. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: Ifc03ac7090e7edbceeac414e908bc5aedb7ad1c3
* tools: remove phosphor-ipmi-blobs dependencyPatrick Venture2019-06-2719-45/+44
| | | | | | | | | | The host tool depended on the BMC header: firmware_handler.hpp because it defined the flags. This header depends on phosphor-ipmi-blobs, therefore the host-tool depends on this. Move the flags into a separate common header file and snip this dependency. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: Id2ad33a1611c02605a1ed5c695429d0451eb98d4
* move bmc code into bmc folderPatrick Venture2019-06-2726-0/+3255
Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I2407359461a1a2f0e733ff8cd0cb1744b6304c32
OpenPOWER on IntegriCloud