PCR 15879 - Add support for boot image archive type with arbitrary binary data.
Summary: Add support for boot image archive type with arbitrary binary data.
Status: ASSIGNED
Alias: None
Product: Kernel
Classification: Deos
Component: Kernel (show other PCRs)
Version: experimental
Hardware: All Deos
: By Cert
: Enhancement
Target Milestone: mainline
Assignee: Sam DiCaro
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2024-08-26 09:17 MST by Sam DiCaro
Modified: 2025-03-27 09:32 MST (History)
2 users (show)

See Also:
Impact Assessment: Trivial
Organization: DDC-I, Inc.
sdicaro: Requirements?
rroffelsen: Code? (sdicaro)
sdicaro: TestCases?
sdicaro: TestProcedures?
sdicaro: Other?

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this PCR.
Description Sam DiCaro 2024-08-26 09:17:06 MST 
Add a new "BIFH_contentType_" for arbitrary binary data in a BIF. In support of the Phased Boot Project needing new BIF archive format.
Comment 1 Sam DiCaro 2024-08-26 11:24:43 MST 
Committed SVNRevision 95024.

Added new Boot Image Content Type for a Binary Archive. Updated release notes.
Comment 2 deosbugs.ccb 2024-08-30 06:56:21 MST 
CCB visited this PCR on 2024-08-30-49739
Comment 3 deosbugs.ccb 2024-08-30 09:07:33 MST 
Developer asserts updates are acceptable for 11.4.0.
Comment 4 deosbugs.ccb 2024-12-11 13:05:42 MST 
CCB visited this PCR on 2024-12-11-68907
Comment 5 rroffelsen 2025-01-10 10:41:50 MST 
I think binary archives should support optionally setting a storageBlockAddress for use by the loader.

The description of BootImageFileHeader_t.storageBlockAddress was weak before this proposal, with this proposal it would be incorrect.

I think the description of BootImageFileHeader_t.storageBlockAddress should be:

 - For LFSs, MFSs: The physical address the loader is expected to load the image to.
 - For image references: The "address" the loader is expected to load the image from. The interpretation of the "address" is loader defined, for example it may be a physical address or it could be an address within a block devices.
 - For archives (composite, selection, and binary) and compressed images: The value is loader defined.
Comment 6 rroffelsen 2025-01-14 08:45:24 MST 
(In reply to rroffelsen from comment #5)

> I think the description of BootImageFileHeader_t.storageBlockAddress should
> be:

Given PCR 16205, perhaps it should be:
 - For LFSs: The physical address the loader is expected to load the
 image to.
 - For image references: The "address" the loader is expected to load the
 image from. The interpretation of the "address" is loader defined, for
 example it may be a physical address or it could be an address within a
 block devices.
 - For MFSs, archives (composite, selection, and binary), and compressed images:
 The value is loader defined.
Comment 7 deosbugs.ccb 2025-03-27 09:32:26 MST 
CCB visited this PCR on 2025-03-27-57605