| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Add the details on how one has to configure a platform to use it.
Although these details are less about the design, they are becoming
relevant.
Change-Id: I11ee48dc768aa424fe6fb5886e030ee172a5c8de
Signed-off-by: Patrick Venture <venture@google.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Simply the verification approach by providing an additional blob_id
whose purpose is to handle triggering verification as well as reporting
verification status.
Originally, this was handled by actions against the hash blob, however
this lead to unnecessary complexity.
Change-Id: Ic63900340abae0dac3453619b6cf1c90b8124504
Signed-off-by: Patrick Venture <venture@google.com>
|
|
|
|
|
|
|
| |
Add details pertaining to the P2A bridge configuration.
Change-Id: I69d1c95fbfbba84cadfaea9c8a89f8416c14d469
Signed-off-by: Patrick Venture <venture@google.com>
|
|
|
|
|
|
|
|
| |
Tweak phrasing for firmware update naming, legacy here can refer to
static.
Change-Id: I4c12dd171999f109fc7309e45d6c3e14326c66e4
Signed-off-by: Patrick Venture <venture@google.com>
|
|
|
|
|
|
|
| |
Update title of firmware update over blobs design.
Change-Id: Ibb2544400ed4258865b6668ac2df303aa8f79e87
Signed-off-by: Patrick Venture <venture@google.com>
|
|
Firmware update process using the Blob protocol over IPMI. This process
will allow legacy and UBI image uploads over IPMI/P2A/LPC with signature
verification. Each platform can provide modifications to the handler
behavior or add custom handlers as needed. The firmware update process
will be just another blob handler and therefore implement the
appropriate blob protocol primitives.
Change-Id: I7e18a7900c878d5d9205a8c1b8475e71a1bceeb3
Signed-off-by: Patrick Venture <venture@google.com>
|