Lines Matching full:blob

1 # BMC Generic Binary Blob Store via OEM IPMI Blob Transport
25 Despite its name, the binary blob store cannot be used for everything.
28   blob store and not try to write it due to concurrency concerns. It is expected
29   the only accessors are the IPMI blob store commands.
40 Please read the IPMI Blob protocol design as primer
41 [here](https://github.com/openbmc/phosphor-ipmi-blobs/blob/master/README.md).
50 1. The host should know the specific blob base id that it intends to operate on.
59 each handler of the IPMI Blob protocol.
61 ### Blob ID Definition
63 A "blob id" is a unique string that identifies a blob. Binary Store handler may
64 show two kinds of blob ids: "base id" and "file id". They should only contain
73 longest matching prefix is considered reserved as a binary blob in the storage
76 For example, if `/test/` and `/test/blob0` are the initial blob ids, we know
77 there is one binary store location with one blob already created. To create a
78 new blob named `/test/blob1`, one simply calls open with the id and write/commit
112   repeated BinaryBlob blob = 2;
120 ### IPMI Blob Transfer Command Primitives
127 a valid binary has successfully been committed, its blob id will appear in the
135 blob.
138 commands to operate on the blob. If there is already an open session, this call
141 NOTE: the newly created blob is not serialized and stored until `BmcBlobCommit`
163 Mark the session as closed. Any uncommitted changes to the blob state is lost.
185    blob with binary data stored, BMC handler only populates the `base_id` per
189 1. `BmcBlobWrite` multiple times to write the data into the blob.
209 I2C devices attached to the BMC. In comparison, the blob store approach proposed
222 **_Host compatibility_**: If data has been stored using IPMI blob binary store,
223 then the host would need a handler that understands the blob transfer semantics