docs/designs/firmware-update-via-blobs.md

9 The BMC needs a mechanism for receiving a new firmware image from the host
19 update mechanism that can be done in-band between the host and the BMC.
39 - Any update mechanism must provide support for UBI tarballs and legacy (static
41   support for any image type simply by implementing a mechanism for handling it.
43 - Any update mechanism must allow for triggering an image verification step
46 - Any update mechanism must allow implementing the data staging via different
49 - Any update mechanism must provide a handshake or equivalent protocol for
54 - Any update mechanism must attempt to maintain security, insomuch as not
82 layout) or the UBI mechanism, or both. The flags provided to the open command
83 identify the mechanism selected by the client-side. The stat command will return
105 | Hash Blob     | Id Mechanism                    |
113 There is only one hash "file" mechanism. The exact hash used will only be
129 | `/flash/verify` | Verify Trigger Mechanism |
140 blob id to trigger the update mechanism.
147 | `/flash/update` | Trigger Update Mechanism |
156 convenient cleanup mechanism.
159 system cleanup mechanism. This could also be accomplished by warm rebooting the
168 of a convenience mechanism instead of a required mechanism.
172 | `/flash/cleanup` | Trigger Cleanup Mechanism |
184 The update mechanism will expect a specific sequence of commands depending on
185 the transport mechanism selected. Some mechanisms require a handshake.
260 The update mechanism will implement the Blob primitives as follows.
265 used for specifying the transport mechanism. To obtain the list of supported
285 mechanism, otherwise it is rejected. If the request is also set for reading,
304 The write command's contents will depend on the transport mechanism. This
345 doing this, if the transport mechanism is not IPMI BT, it'll shut down the
346 mechanism used for transport preventing the host from updating anything.
377 In the event the update is already in progress, such as the tarball mechanism is
408 If it's called and the data transport mechanism is P2A, it'll return a 32-bit
522 [Secure Flash Update Mechanism](https://github.com/openbmc/phosphor-ipmi-flash/blob/master/README.m…