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

Tom Rini trini at konsulko.com
Tue Jul 5 21:04:28 CEST 2022

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 <sjg at chromium.org> 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 of one project.
> >
> > Given its close relationship to device tree, I suggest github.com/devicetree-org
> In my mind this effort is similar to EBBR since the goal is to be
> architecture agnostic.
> I am not too picky on the location myself as long as it's open and
> other people can contribute and propose changes.

I agree with this sentiment.  And to the extent that being distributed
is a good thing (and I believe it is), a good governance model and ease
of contribution matters more-so than hosting location and to that end,
git.trustedfirmware.org / reviews.trustedfirmware.org (which I see lets
you use GitHub to sign-in/auth) makes sense to me.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20220705/374d66ad/attachment.sig>

More information about the U-Boot mailing list