-
Notifications
You must be signed in to change notification settings - Fork 18
Clarify in README that v0.9 and v1.0 are withdrawn #80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+6
−7
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,6 +6,8 @@ This repository contains the Firmware Handoff specification, which defines a | |
| data structure to transfer essential configuration information between firmware | ||
| stages during platform initialization. | ||
|
|
||
| Note that versions 0.9 and 1.0 of this specification are withdrawn and should not be used for product development. | ||
|
|
||
| The documentation is generated using the Sphinx framework. A version of this | ||
| specification, rendered in HTML, is available | ||
| [here](https://firmwarehandoff.github.io/firmware_handoff/). | ||
|
|
@@ -47,11 +49,8 @@ The output of these build commands goes into subdirectory `build`. | |
| Status | ||
| ====== | ||
|
|
||
| The first release of the specification has been published. We are currently in | ||
| the implementation phase, looking at various target projects, including U-Boot, | ||
| coreboot, TF-A and Tianocore. Once this is done we will review the result to see | ||
| if any serious flaws have come to light, meaning that changes are needed. If | ||
| so, these will be undertaken in each project. | ||
| As of November 2025, version 1.0 is withdrawn and should not be used. | ||
| Version 1.0 was withdrawn because products shipped with a TL header cheksum implementation that differed from the version 1.0 definition. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. minor: I think this file generally tries to stick to an 80 column limit. |
||
|
|
||
| By the end of 2024, the spec will be considered stable and will be published | ||
| as version 1. From there on, backwards compatibility will be maintained. | ||
| A version 2.0 of the specification is currently under work and will be published shortly. | ||
| Implementations should adopt version 2.0 of the specification. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think all the changes should be in the status section below, which is no longer accurate at all. Also, those versions are withdrawn, not deprecated. I think you could also say this is due to a mismatch in the checksum algorithm in the spec versus implementations (at least in the commit message).