Capsule update for RPI_EFI.FD

[andreiw]

Even though this is just a file on SD, we should aim to have a sample implementation, as SBBR requires capsule. There are constraints given to how the Pi boots, though...

[jlinton]

Oh, I thought there was a capsule update bug in here, moving comments from the other one here:

The current Pi4 firmware update process is, well, not ideal. The user should be able to run fwupdmgr update against the rpi when running in linux/etc and see the machine firmware status, as well as be able to actually upgrade it without downloading/unzipping/etc the files provided here.

At a minimum, we should start filling out the ERST data, then allow local capsule upgrades, and then pull those capsules via LVFS.

As a starting place:

[root@rpi4-f35 ~]# fwupdmgr get-devices Raspberry Pi 4 Model B │ ├─CS1311 240GB SSD: │ Device ID: fe3e29da68b8473a53f8f1b134fab9748e69859b │ Summary: ATA drive │ Current version: CS131122 │ Vendor: PNY (ATA:0x196E, OUI:f8db4c) │ Serial Number: PNYXXXXXX │ GUIDs: 99d1118b-f876-5322-92b3-68f987e4fd13 ← IDE\PNY_CS1311_240GB_SSD____________________CS131122 │ e97987d3-20f7-55bc-bed7-46ffa113e566 ← IDE\0PNY_CS1311_240GB_SSD____________________ │ 4b8ad262-120a-5cf8-bc6a-c5a11499b659 ← PNY CS1311 240GB SSD │ Device Flags: • Updatable │ • System requires external power source │ • Needs a reboot after installation │ └─UEFI Device Firmware: Device ID: a45df35ac0e948ee180fe216a5f703f32dda163f Summary: UEFI ESRT device Current version: 0 Minimum Version: 1 Vendor: DMI:EDK2 Update State: Success GUIDs: b3ac26c8-71e7-4a0b-8116-40600611f43e e8d71b10-075d-5177-afc0-7db5649412cd ← UEFI\RES_{b3ac26c8-71e7-4a0b-8116-40600611f43e} Device Flags: • Internal device • Updatable • System requires external power source • Supported on remote server • Needs a reboot after installation • Device is usable for the duration of the update