ivasakthivel Nainar
> ; Samer El-Haj-Mahmoud mahm...@arm.com>; nd
> Subject: RE: [TF-A] [RFC] Proposed location to host the firmware handoff
> specification.
>
> Hi Julius
>
> > -Original Message-
> > From: Julius Werner
> > Sent: 06 December 202
> OK, this seems to be the crux of the problem. Is it possible for us say that
> users are free to register new TLs, while at the same time recommending the
> use of existing formats for complex structures (e.g. FDT, HOB)?
I'm not really sure what qualifies as a "complex structure" in this
discu
On 12/5/22 10:18 PM, Julius Werner via TF-A wrote:
It seems like some of us still have very different opinions about how
this handoff structure should and shouldn't be used, which I really
think need to be worked out and then codified in the spec before we
can call the document final, because
Hi Julius
> -Original Message-
> From: Julius Werner
> Sent: 06 December 2022 04:18
>
> It seems like some of us still have very different opinions about how this
> handoff structure should and shouldn't be used, which I really think need to
> be worked out and then codified in the spec
It seems like some of us still have very different opinions about how
this handoff structure should and shouldn't be used, which I really
think need to be worked out and then codified in the spec before we
can call the document final, because otherwise no firmware project can
trust that it is safe
ose Marinho ; t...@lists.trustedfirmware.org;
> > u-boot@lists.denx.de; boot-architect...@lists.linaro.org; Manish Pandey2
> > ; Joanna Farley ;
> > Ilias Apalodimas ; Matteo Carlini
> > ; Dan Handley ; Rob
> > Herring ; Harb Abdulhamid
> > (h...@amperecomputing.
; boot-architect...@lists.linaro.org; Manish Pandey2
> ; Joanna Farley ;
> Ilias Apalodimas ; Matteo Carlini
> ; Dan Handley ; Rob
> Herring ; Harb Abdulhamid
> (h...@amperecomputing.com) ;
> Sivasakthivel Nainar ; Samer El-Haj-
> Mahmoud ; nd
> Subject: Re: [TF-A] [RFC] P
Hi,
On Wed, 30 Nov 2022 at 16:48, Julius Werner wrote:
>
> Okay, FWIW I created a pull request with my suggestions here:
> https://github.com/FirmwareHandoff/firmware_handoff/pull/4
>
> That should make it easier to discuss specific details, hopefully. As
> I was looking at the header size and fo
Okay, FWIW I created a pull request with my suggestions here:
https://github.com/FirmwareHandoff/firmware_handoff/pull/4
That should make it easier to discuss specific details, hopefully. As
I was looking at the header size and format more closely I noticed
that the checksum calculation and some d
Hi,
On Wed, 30 Nov 2022 at 14:52, Julius Werner wrote:
>
> Hi Jose,
>
> Apologies for the late response, I had to find some time to dig back
> into this topic first.
>
> > The proposal is that the tag assignments are handled via a PR to [1].
> > A PR should provide reasoning for the proposed entr
Hi Jose,
Apologies for the late response, I had to find some time to dig back
into this topic first.
> The proposal is that the tag assignments are handled via a PR to [1].
> A PR should provide reasoning for the proposed entry layout as well as a
> description of the use-case being serviced.
>
Jose Marinho ; Simon Glass
> ; Dan Handley
> Cc: t...@lists.trustedfirmware.org; u-boot@lists.denx.de; boot-
> architect...@lists.linaro.org; nd
> Subject: RE: [TF-A] Re: [RFC] Proposed location to host the firmware handoff
> specification.
>
> Hi,
>
> Thanks for the emai
...@lists.trustedfirmware.org; u-boot@lists.denx.de;
boot-architect...@lists.linaro.org; nd
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 source
Hi Julius,
Thank you for the comments!
As mentioned yesterday, the FW Handoff document is now publicly accessible from
[1] -- note that this does not constitute a full document release.
Hopefully we'll be able to use that repo to agree on the open items before we
do an initial full release of t
Sunday, September 18, 2022 4:05 AM
To: Dan Handley
Cc: t...@lists.trustedfirmware.org; u-boot@lists.denx.de;
boot-architect...@lists.linaro.org; nd
Subject: Re: [TF-A] Re: [RFC] Proposed location to host the firmware handoff
specification.
Hi,
I discussed this with Jose a white back. I a
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 wrote:
>
> Hi all
>
> Just picking up this old thread
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 th
> That draft is the DEN0135 document [2].
> I realise that I haven’t made it sufficiently explicit in this thread that
> the DEN0135 document [2] is still at draft quality (see ALP maturity called
> out in the title page and footers).
> Please do not consider this a finished document 😊. We’ve bee
Hi Julius,
Thanks for reviewing the draft proposal, and for your comments.
Last year’s discussion concluded with the agreement that, as a next step, we
would draft a proposal of the data structure [1].
That draft is the DEN0135 document [2].
I realise that I haven’t made it sufficiently explici
Hi Jose,
Can you provide a bit more background on where this proposal suddenly
came from and what considerations went into its design? The mailing
list discussion from last year sort of petered out without much
concrete agreement, and now you're here with a full specification.
It's hard to provide
Ilias Apalodimas ;
> Matteo Carlini ; Dan Handley
> ; Harb Abdulhamid
> (h...@amperecomputing.com) ; Samer El-
> Haj-Mahmoud ; nd
> Subject: RE: [RFC] Proposed location to host the firmware handoff
> specification.
>
> Hi,
>
> My concern with a standalone gitlab proj
t-architect...@lists.linaro.org; François Ozog
> ; Manish Pandey2 ;
> Joanna Farley ; Ilias Apalodimas
> ; Matteo Carlini
> ; Dan Handley ; Harb
> Abdulhamid
> (h...@amperecomputing.com) ; Samer El-
> Haj-Mahmoud ; nd
> Subject: Re: [RFC] Proposed location to host the firmw
as Apalodimas
> ; Matteo Carlini ;
> Dan Handley ; Harb Abdulhamid
> (h...@amperecomputing.com) ; Samer El-
> Haj-Mahmoud ; nd
> Subject: Re: [RFC] Proposed location to host the firmware handoff
> specification.
>
> Hi Rob,
>
> On Tue, 5 Jul 2022 at 11:27, Rob H
Hi Rob,
On Tue, 5 Jul 2022 at 11:27, Rob Herring wrote:
>
> On Tue, Jul 5, 2022 at 10:37 AM Simon Glass wrote:
> >
> > Hi Rob,
> >
> > On Tue, 5 Jul 2022 at 09:24, Rob Herring wrote:
> > >
> > > On Thu, Jun 30, 2022 at 3:24 AM Simon Glass wrote:
> > > >
> > > > Hi Jose,
> > > >
> > > > I don't
On Thu, Jun 30, 2022 at 01:40:11PM +0300, Ilias Apalodimas wrote:
> Hi all,
>
> Thanks for pushing on this
>
> On Thu, 30 Jun 2022 at 12:24, Simon Glass wrote:
> >
> > Hi Jose,
> >
> > I don't think this is correct. TF-A is a project that aims to replace
> > U-Boot SPL (and perhaps other compone
On Tue, Jul 5, 2022 at 10:37 AM Simon Glass wrote:
>
> Hi Rob,
>
> On Tue, 5 Jul 2022 at 09:24, Rob Herring wrote:
> >
> > On Thu, Jun 30, 2022 at 3:24 AM Simon Glass wrote:
> > >
> > > Hi Jose,
> > >
> > > I don't think this is correct. TF-A is a project that aims to replace
> > > U-Boot SPL (a
Hi Rob,
On Tue, 5 Jul 2022 at 09:24, Rob Herring wrote:
>
> On Thu, Jun 30, 2022 at 3:24 AM Simon Glass wrote:
> >
> > Hi Jose,
> >
> > I don't think this is correct. TF-A is a project that aims to replace
> > U-Boot SPL (and perhaps other components) with more closed firmware,
> > e.g. the perm
On Thu, Jun 30, 2022 at 3:24 AM Simon Glass wrote:
>
> Hi Jose,
>
> I don't think this is correct. TF-A is a project that aims to replace
> U-Boot SPL (and perhaps other components) with more closed firmware,
> e.g. the permissive license.
>
> This spec needs to be in a neutral place, not captive
Hi Simon
A couple of important points:
* TF-A does not aim to replace U-Boot SPL; it aims to reduce fragmentation in
secure firmware. The permissive license may not be ideal but from an OSS PoV,
but it enables much wider adoption than other licensing schemes. But that's
perhaps a philosophical
Hi all,
Thanks for pushing on this
On Thu, 30 Jun 2022 at 12:24, Simon Glass wrote:
>
> Hi Jose,
>
> I don't think this is correct. TF-A is a project that aims to replace
> U-Boot SPL (and perhaps other components) with more closed firmware,
> e.g. the permissive license.
>
> This spec needs to
Hi Jose,
I don't think this is correct. TF-A is a project that aims to replace
U-Boot SPL (and perhaps other components) with more closed firmware,
e.g. the permissive license.
This spec needs to be in a neutral place, not captive of one project.
Given its close relationship to device tree, I su
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 fi
32 matches
Mail list logo
