On Thu, Sep 14, 2023 at 05:42:49PM +0530, Sughosh Ganu wrote:
hi Tom,
On Thu, 14 Sept 2023 at 00:54, Tom Rini trini@konsulko.com wrote:
On Fri, Sep 08, 2023 at 05:29:54PM +0530, Sughosh Ganu wrote:
Recently, a set of patches were merged in next, which were adding support for generating capsules as part of the U-Boot build. Mid way through the review of those patches, it was decided to drop the patches for generating capsules through a config file. That was primarily due to the use of absolute paths in binman for testing the capsule genertion through config file. Now that the base set of patches have been merged, this series is picking up the remaining patches for review. This series addresses the concern that Simon Glass had with the use of absolute paths.
The first set of patches are adding support for generating capsules by parsing the capsule parameters through a config file, and adding a binman entry type for this. These are patches 1-5.
The other set of patches is for generating empty accept and revert capsules through binman. These capsules are needed for the FWU A/B update functionality.
I think what we really need next is to be able to implement and document how to use the capsule (and FWU!) spec / mechanisms on another platform and I think the Synquacer DeveloperBox would be a good target here as I believe you have access to one and so does Simon to we can deal with feedback on a real platform that both of you have access to.
That should be possible. And although I personally don't have access to the board, folks in the team do(including Ilias). I will work on this once the patches for supporting empty capsules in binman get merged.
We need to make this the next task as not being able to put this to use on a real platform today is blocking understanding of what abstractions do and don't make real sense. To tie this to another thread, since it's not really clear how a real platform would make use of capsules it's not really clear what sandbox should make every time.