Hi,
Do we have slides and video from last week's discussion?
Thanks,
Okash
On Wed, May 5, 2021 at 11:52 PM Simon Glass via TF-A
wrote:
>
> Hi Harb,
>
> Thanks for the idea. I am still not completely sure what benefit UUID
> provides to an open project. I'd like to propose something different, more in
> the spirit of open collaboration. I also worry that the word 'standard' seems
> to be a synonym for UUIDs, UEFI, etc., i.e. enabling/preferring closed-source
> firmware and the continued decline of open-source projects. It really should
> not be.
>
> So I suggest: Use simple integer IDs and reserve some area for 'private' use.
> If you want to collaborate across projects outside your company, you either
> need to allocate a 'public' ID or agree privately between the parties which
> private ID to use.
>
> This means that the default and easiest option is for collaboration and a
> public ID, with private ones (whose purpose may be secret) reserved just for
> private use.
>
> Regards,
> Simon
>
> On Wed, 5 May 2021 at 11:42, Harb Abdulhamid OS
> wrote:
>>
>> Hey Folks,
>>
>> We wanted to put out a middle-ground proposal to help guide the discussion
>> on the call tomorrow.
>>
>>
>>
>> A proposal that we have been discussing offline involves reserving a single
>> tag ID for the purpose of construction UEFI PI HOB List structure, and that
>> tag would be used to identify a HOB-specific structure that does leverage
>> UUID based identifier. This will eliminate the burden of having to support
>> UUID as the tag, and this enables projects that require UUID based
>> identifiers for the broad range of HOB structures that need to be produced
>> during the booting of the platform. Once we have a tag for a HOB list, this
>> will enable various HOB producers that can add/extend the HOB list in TF-A
>> code (or even pre-TF-A code), with a HOB consumer for that UUID/GUID on the
>> other side (i.e. whatever the BL33 image is booting on that platform).
>>
>>
>>
>> Essentially, the idea is if someone would like to support HOB structures in
>> a standard way using TF-A, they would wrap it up in a BL_AUX_PARAM/BLOB
>> structure (whatever the group decides) and the way we identify the structure
>> as a HOB list is with this new reserved tag.
>>
>>
>>
>> Hopefully that makes sense and less contentious. Look forward to discuss
>> this further on the call.
>>
>>
>>
>> Thanks,
>>
>> --Harb
>>
>>
>>
>> From: Manish Pandey2
>> Sent: Friday, April 30, 2021 8:14 AM
>> To: François Ozog
>> Cc: Simon Glass ; Julius Werner ;
>> Harb Abdulhamid OS ; Boot Architecture
>> Mailman List ;
>> t...@lists.trustedfirmware.org; U-Boot Mailing List ;
>> Paul Isaac's ; Ron Minnich
>> Subject: Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for
>> information passing between boot stages
>>
>>
>>
>> Hi All,
>>
>>
>>
>> Please find invite for next TF-A Tech Forum session to continue our
>> discussions on HOB implementation, feel free to forward it to others.
>>
>>
>>
>> The next TF-A Tech Forum is scheduled for Thu 6th May 2021 16:00 – 17:00
>> (BST).
>>
>>
>>
>> Agenda:
>>
>> Discussion Session: Static and Dynamic Information Handling in TF-A
>>
>> Lead by Manish Pandey and Madhukar Pappireddy
>>
>> · There is ongoing mailing lists discussion[1] related with adopting
>> a mechanism to pass information through boot stages.
>>
>> The requirement is two-fold:
>>
>> 1. Passing static information(config files)
>>
>> 2. Passing dynamic information (Hob list)
>>
>> In the upcoming TF-A tech forum, we can start with a discussion on dynamic
>> information passing and if time permits, we can cover static information
>> passing. The purpose of the call is to have an open discussion and continue
>> the discussion from the trusted-substrate call[2] done earlier. We would
>> like to understand the various requirements and possible ways to implement
>> it in TF-A in a generalized way so that it can work with other Firmware
>> projects.
>>
>>
>>
>> The two specific item which we would like to discuss are:
>>
>> 1. HOB format: TF-A/u-boot both has an existing bloblist
>> implementation, which uses tag values. Question, can this be enhanced to use
>> hybrid values(Tag and UUID) both?
>>
>> 2. Standardization on Physical register use to pass base of HoB data
>> structure.
>>
>> References:
>>
>> [1] https://lists.trustedfirmware.org/pipermail/tf-a/2021-April/001069.html
>>
>> [2]
>> https://linaro-org.zoom.us/rec/share/zjfHeMIumkJhirLCVQYTHR6ftaqyWvF_0klgQnHTqzgA5Wav0qOO8n7SAM0yj-Hg.mLyFkVJNB1vDKqw_
>> Passcode: IPn+5q%
>>
>>
>>
>> Thanks
>>
>>
>>
>> Joanna
>>
>>
>>
>> You have been invited to the following event.
>>
>> TF-A Tech Forum
>>
>> When
>>
>> Every 2 weeks from 16:00 to 17:00 on Thursday United Kingdom Time
>>
>> Calendar
>>
>> t...@lists.trustedfirmware.org
>>
>> Who
>>
>> •
>>
>> Bill Fletcher- creator
>>
>> •
>>
>> t...@lists.trustedfirmware.org
>>
>> more details »
