boot-architecture November 2022

boot-architecture@lists.linaro.org

7 participants
7 discussions

[RFC] Proposed location to host the firmware handoff specification.

by Jose Marinho

Hi, Arm worked to draft a firmware handoff [1] specification, evolving it based on community feedback. This activity followed the request of some members of the Arm ecosystem [2]. The spec (still at ALP – feedback/comments welcome!) standardizes how information is propagated between different firmware components during boot. The spec hopes to remove the reliance on bespoke/platform-specific information handoff mechanisms, thus reducing the code maintenance burden. The concept of entry types is present in the spec – these are data structure layouts that carry a specific type of data. New types are meant to be added, following the needs and use-cases of the different communities. Thus, these communities should be empowered to request new types! To enable community contributions, the specification must be hosted in a location that is friendly to change requests. We propose to host the spec in trustedfirmware.org (tf.org). Tf.org hosts several open-source projects and already has an open governance model. TF-A, and the associated community, rely on tf.org, and thus are already well equipped to maintain this specification and keep it up to date. Tf.org is agnostic of any downstream projects that would adopt this specification (e.g. U-boot, EDK2, etc.). We welcome the views of the communities and want to understand if there are any strong objections to what’s being proposed! If anyone has objections, we are happy to consider alternatives and associated trade-offs. Regards [1] https://developer.arm.com/documentation/den0135/latest [2] Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages - TF-A - lists.trustedfirmware.org<https://lists.trustedfirmware.org/archives/list/tf-a@lists.trustedfirmware.…>

1 year, 7 months

There will be NO DT call on Monday Nov 28

by Bill Mills

All, Next Monday the US will still be recovering/traveling from the holiday extended weekend. So we will cancel the call. Happy Thanksgiving to everyone that celebrates. Thanks, Bill -- Bill Mills Principal Technical Consultant, Linaro +1-240-643-0836 TZ: US Eastern Work Schedule: Tues/Wed/Thur

2 years

We will have an EBBR call today

by Vincent Stehlé

Hi, We will have an EBBR call[1] today at 15h UTC/BST. On the agenda[2]: - Preparing for next version 2.x.y (UEFI 2.10, ESRT, etc.) - Version numbering and corresponding update to conformance profile - Issues[3] scrub - Can we define a minimum viable product (MVP)? - Does this help? - Is Security in? Feel free to add to the agenda, directly on the wiki page or by e-mail. We can use this pad[4] for the meeting notes. Best regards, Vincent Stehlé System Architect - Arm [1]: https://armltd.zoom.us/j/92081365511?pwd=SFZpRitXUEp3Zy9GM0h3UUZ1b1pnUT09 [2]: https://github.com/ARM-software/ebbr/wiki/EBBR-Meetings [3]: https://github.com/ARM-software/ebbr/issues [4]: https://mensuel.framapad.org/p/ebbr-meeting-of-2022-11-21-9xq8

2 years, 1 month

RE: [TF-A] Re: [RFC] Proposed location to host the firmware handoff specification.

by Dan Handley

Hi Varun Yes, I think the GitHub issue tracker can be used for all those things. Also, the TF-A list can be used for general questions/discussion - that has more visibility. Cheers Dan. > -----Original Message----- > From: Varun Wadekar <vwadekar(a)nvidia.com> > Sent: 15 November 2022 15:29 > To: Jose Marinho <Jose.Marinho(a)arm.com>; Simon Glass > <sjg(a)chromium.org>; Dan Handley <Dan.Handley(a)arm.com> > Cc: tf-a(a)lists.trustedfirmware.org; u-boot(a)lists.denx.de; boot- > architecture(a)lists.linaro.org; nd <nd(a)arm.com> > Subject: RE: [TF-A] Re: [RFC] Proposed location to host the firmware handoff > specification. > > Hi, > > Thanks for the email. Jose, how do we create bugs, provide ideas, or ask > questions? Do you suggest creating issues for all of these? > > -Varun > > -----Original Message----- > From: Jose Marinho via TF-A <tf-a(a)lists.trustedfirmware.org> > Sent: Monday, 14 November 2022 3:30 PM > To: Simon Glass <sjg(a)chromium.org>; Dan Handley > <Dan.Handley(a)arm.com> > Cc: tf-a(a)lists.trustedfirmware.org; u-boot(a)lists.denx.de; boot- > architecture(a)lists.linaro.org; nd <nd(a)arm.com> > Subject: [TF-A] Re: [RFC] Proposed location to host the firmware handoff > specification. > > External email: Use caution opening links or attachments > > > Hi, > > We're glad to announce that the Firmware Handoff document sources are > now available publicly from: > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith > ub.com%2FFirmwareHandoff%2Ffirmware_handoff&data=05%7C01%7 > Cvwadekar%40nvidia.com%7C1802d934994a45de3f4f08dac655668a%7C43083 > d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638040367718884340%7CUnkn > own%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik > 1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=G1T9ndA4NlbTJ > vQ%2BuWVu1S%2FQNjGkA6HicXD%2FS%2FuaG8Q%3D&reserved=0 > > Note that this does not constitute a full "1.0" release of the document. > There are still some topics raised in the ML that need to be aligned on before > the full release -- I'll follow up on those with a separate e-mail. > > Having the document hosted in a public repo allows for all discussions about > the document to progress in the open more easily. > > Regards, > Jose > > -----Original Message----- > From: Simon Glass <sjg(a)chromium.org> > Sent: Sunday, September 18, 2022 4:05 AM > To: Dan Handley <Dan.Handley(a)arm.com> > Cc: tf-a(a)lists.trustedfirmware.org; u-boot(a)lists.denx.de; boot- > architecture(a)lists.linaro.org; nd <nd(a)arm.com> > Subject: Re: [TF-A] Re: [RFC] Proposed location to host the firmware handoff > specification. > > Hi, > > I discussed this with Jose a white back. I am OK with this as an interim > measure to get the initial doc agreed, so long as we move it to a more > independent place when available. > > Regards, > Simon > > > > On Tue, 13 Sept 2022 at 09:48, Dan Handley <Dan.Handley(a)arm.com> wrote: > > > > Hi all > > > > Just picking up this old thread again... > > > > There seemed to be general agreement to host the firmware hand-off > spec in a separate repo with separate maintainers at TrustedFirmware.org, at > least initially. Arm intends to progress with the initial population of this repo. > We intend to use the CC-BY-SA-4.0 > (https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fspd > x.org%2Flicenses%2FCC-BY-SA- > 4.0.html&data=05%7C01%7Cvwadekar%40nvidia.com%7C1802d934994a > 45de3f4f08dac655668a%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0% > 7C638040367718884340%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAw > MDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C% > 7C&sdata=eB3APd46h8VOPyIPSd1XtIiAziKVr6GMTX3T2UAT39c%3D&am > p;reserved=0) license, the same as used for EBBR > (https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith > ub.com%2FARM- > software%2Febbr&data=05%7C01%7Cvwadekar%40nvidia.com%7C1802 > d934994a45de3f4f08dac655668a%7C43083d15727340c1b7db39efd9ccc17a%7 > C0%7C0%7C638040367719040563%7CUnknown%7CTWFpbGZsb3d8eyJWIjoi > MC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300 > 0%7C%7C%7C&sdata=w%2FKV4fHrVWZKkDjtQOAFhkUr6axGHLnKhGCp > 2fcbb74%3D&reserved=0). Please say if you have any objections to this. > We will also seek approval from the TrustedFirmware.org board. > > > > Regards > > > > Dan. > > > > _______________________________________________ > > boot-architecture mailing list -- boot-architecture(a)lists.linaro.org > > To unsubscribe send an email to > > boot-architecture-leave(a)lists.linaro.org > _______________________________________________ > boot-architecture mailing list -- boot-architecture(a)lists.linaro.org > To unsubscribe send an email to boot-architecture-leave(a)lists.linaro.org > -- > TF-A mailing list -- tf-a(a)lists.trustedfirmware.org To unsubscribe send an > email to tf-a-leave(a)lists.trustedfirmware.org

2 years, 1 month

RE: [TF-A] Re: [RFC] Proposed location to host the firmware handoff specification.

by Dan Handley

Hi all Just picking up this old thread again... There seemed to be general agreement to host the firmware hand-off spec in a separate repo with separate maintainers at TrustedFirmware.org, at least initially. Arm intends to progress with the initial population of this repo. We intend to use the CC-BY-SA-4.0 (https://spdx.org/licenses/CC-BY-SA-4.0.html) license, the same as used for EBBR (https://github.com/ARM-software/ebbr). Please say if you have any objections to this. We will also seek approval from the TrustedFirmware.org board. Regards Dan.

2 years, 1 month

DT Call tomorrow

by Bill Mills

All, We will have the Devicetree call tomorrow. The topic will be DT best practice in U-boot. Simon will only be able to join for the first 30 minutes so lets start on time please. Thanks, Bill Topic: Devicetree Evolution Time: Oct 18, 2021 3pm UK time Every 2 weeks on Mon Please download and import the following iCalendar (.ics) files to your calendar system. Weekly: https://linaro-org.zoom.us/meeting/tJIscOmsrDMiGtWio_TMUjXFfAk0Ivr_fr03/ics… Join Zoom Meeting https://linaro-org.zoom.us/j/96170428801?pwd=elBJNFdVMFJub0UzanFUcVQxTHBqdz… Meeting ID: 961 7042 8801 Passcode: 8250 One tap mobile +13017158592,,96170428801# US (Washington DC) +16465588656,,96170428801# US (New York) Find your local number: https://linaro-org.zoom.us/u/acQEZ30MEP -- Bill Mills Principal Technical Consultant, Linaro +1-240-643-0836 TZ: US Eastern Work Schedule: Tues/Wed/Thur

2 years, 1 month

Topics for the EBBR call?

by Vincent Stehlé

Hi, For the moment we have no topic for the EBBR call today[1]. Let's give people until noon (UTC) to propose topics, otherwise we can skip this call. Best regards, Vincent Stehlé System Architect - Arm [1]: https://github.com/ARM-software/ebbr/wiki/EBBR-Meetings

2 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

boot-architecture November 2022