Skip to content

Complete Pj-specific TE move to separatate spec#85

Open
jmarinho wants to merge 1 commit intomainfrom
move_TEs_to_project_specific_spec
Open

Complete Pj-specific TE move to separatate spec#85
jmarinho wants to merge 1 commit intomainfrom
move_TEs_to_project_specific_spec

Conversation

@jmarinho
Copy link
Contributor

@jmarinho jmarinho commented Jan 6, 2026

The TEs specific to a project (or a small collection or projects) were moved to a separate spec
(https://github.com/FirmwareHandoff/ProjectEntries).

The main FW Handoff spec only carries the tag id list for those TEs. Any new TE declared in the separate spec, must have its tag id listed in the main FW Handoff spec.

Change-Id: If718d948dc4cd4d87d537474538f0ea64865b0e9

Copy link
Contributor

@danh-arm danh-arm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll need to take care that the TEs in the other repo are sync'd with this one when we merge this.


.. [SPMCATTR] `The SPMC manifest v2.12: <https://hafnium.readthedocs.io/en/v2.12.0/secure-partition-manager/secure-partition-manager.html#spmc-manifest>`__

.. [FWH_Project_Entries] `Firmware Handoff Project Entries <https://github.com/FirmwareHandoff/ProjectEntries>`__ No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the ProjectEntries repo name is too generic. Suggest ProjectTransferEntries or ProjectTEs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renamed the repo to ProjectTEs (https://github.com/FirmwareHandoff/ProjectTEs) and updated this reference.


* - :ref:`0x109 <tab_gpt_info>`
* - 0x109
- GPT Error Info
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be more maintainable if you just reserve out the TagID ranges in this spec rather than summarising the TagIDs and their names. It might be good to reserve out a larger block now to avoid updating this spec when adding new TF TEs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed the table to list the ranges in ProjectTEs.

- data_size
- hdr_size
- The `gpt_error_info` field contains GPT error information.
Whenever a new project specific transfer entry is declared in the ancillary specification [FWH_Project_Entries]_, its tag id must be documented in :numref:`tab_entries_summary`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you take my other comment than you can change this to say that this spec must be updated when that spec defines a new TE outside the reserved range(s).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated to:
"Whenever a new tag id range is declared in the ancillary specification [FWH_Project_Entries]_, or an existing tag id range is extended, :numref:tab_entries_summary must be updated accordingly."

The TEs specific to a project (or a small collection or projects) were
moved to a separate spec
(https://github.com/FirmwareHandoff/ProjectTEs).

The main FW Handoff spec only carries the tag id range list for those TEs.
Any new tag id range declared in the separate spec, must be documented in
the main FW Handoff spec.

Change-Id: If718d948dc4cd4d87d537474538f0ea64865b0e9
Signed-off-by: Jose Marinho <jose.marinho@arm.com>
@jmarinho jmarinho force-pushed the move_TEs_to_project_specific_spec branch from 7aec2fc to 7fa1312 Compare January 22, 2026 11:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants