coreboot

Thank you for creating the issue. The problem is, that this is outside of coreboot’s scope.

First, the coreboot project does not distribute images. Second, it’s outside of coreboot’s scope to just initialize the hardware. It would need to be integrated into an existing payload or a new payload needs to be created.

Richard Hughes has looked into integrating (lib)flashrom into fwupd in the past. I have no idea of the status.

So, I am unsure, what to do with your issue. Maybe it should be closed, and you can start a discussion on the coreboot list (and fwupd list if there is one).

Thanks for the explanation. I'll leave it up to you how to handle this issue further.

Regards

Paul Menzel wrote:

Thank you for creating the issue. The problem is, that this is outside of coreboot’s scope.

First, the coreboot project does not distribute images. Second, it’s outside of coreboot’s scope to just initialize the hardware. It would need to be integrated into an existing payload or a new payload needs to be created.

Richard Hughes has looked into integrating (lib)flashrom into fwupd in the past. I have no idea of the status.

So, I am unsure, what to do with your issue. Maybe it should be closed, and you can start a discussion on the coreboot list (and fwupd list if there is one).

Jakob Jakobson wrote:

Dear developers,

could you provide LVFS (Linux Vendor Firmware Service, https://fwupd.org/) support? This could massively simplify coreboot updates for non-expert users.

Regards

Jakob
Since fwupd 1.5.6, it's supported - the vendors just need to upload their rom's.