Skip to content

Commit dfb62d8

Browse files
committed
Clarify in README that v0.9 and v1.0 are withdrawn
Update Readme: - state that v1.0 is withdrawn - set expectations for v2.0 release timeline The version v.9 and v1.0 are withdrawn because products shipped with a TL header checksum implementation that differed from what was spec'd (implementations used sum-based checksum, whereas spec mandated xor). Change-Id: Ibff46e7d88fcec0b1f3352aa7cebd7f5a7204e47 Signed-off-by: Jose Marinho <jose.marinho@arm.com>
1 parent 32c8d72 commit dfb62d8

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

README.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ This repository contains the Firmware Handoff specification, which defines a
66
data structure to transfer essential configuration information between firmware
77
stages during platform initialization.
88

9+
Note that versions 0.9 and 1.0 of this specification are withdrawn and should not be used for product development.
10+
911
The documentation is generated using the Sphinx framework. A version of this
1012
specification, rendered in HTML, is available
1113
[here](https://firmwarehandoff.github.io/firmware_handoff/).
@@ -60,11 +62,8 @@ The U-Boot project hosts another library implementation, referred to as Bloblist
6062
Status
6163
======
6264

63-
The first release of the specification has been published. We are currently in
64-
the implementation phase, looking at various target projects, including U-Boot,
65-
coreboot, TF-A and Tianocore. Once this is done we will review the result to see
66-
if any serious flaws have come to light, meaning that changes are needed. If
67-
so, these will be undertaken in each project.
65+
As of November 2025, version 1.0 is withdrawn and should not be used.
66+
Version 1.0 was withdrawn because products shipped with a TL header cheksum implementation that differed from the version 1.0 definition.
6867

69-
By the end of 2024, the spec will be considered stable and will be published
70-
as version 1. From there on, backwards compatibility will be maintained.
68+
A version 2.0 of the specification is currently under work and will be published shortly.
69+
Implementations should adopt version 2.0 of the specification.

0 commit comments

Comments
 (0)