From: Ferass El Hafidi <vitali64pmemail@protonmail.com>
To: neil.armstrong@linaro.org, Simon Glass <sjg@chromium.org>
Cc: u-boot-amlogic@groups.io, u-boot@lists.denx.de,
alpernebiyasak@gmail.com, linux-amlogic@lists.infradead.org,
mark.kettenis@xs4all.nl
Subject: Re: [PATCH v2 0/1] meson: Demonstration of using binman to produce the image
Date: Thu, 31 Aug 2023 10:25:40 +0000 [thread overview]
Message-ID: <CV6NO816M3FH.30VZXHR4KDM49@flaptop> (raw)
In-Reply-To: <d94b0cae-99cc-4f8b-9d0d-52a5858f6e33@linaro.org>
Hi Simon,
On Thu Aug 31, 2023 at 9:54 AM CEST, neil.armstrong wrote:
> > Thanks for your efforts on this. I look forward to seeing where it ends up.
I hope we can get it to at least boot!
> >> Honestly, in my opinion, including proprietary and poorly-written
> >> Amlogic utilities lacking a proper license, into U-Boot looks like a bad idea.
> >
> > With Binman, we don't really include them in U-Boot; we allow them to
> > be fetched easily so that a complete build can be produced.
Acknowledged.
> > I don't like it either, but for users it is better than doing the
> > build manually.
>
> I'll rather spend time and effort to have a fully-upstream TF-A boot chain
> for Amlogic SoC (when possible) that maintaining support for bulky closed-source
> x86-64 binary only tools. The tools aren't even officially distributed.
I agree with Neil here. I think having U-Boot SPL for Amlogic SoCs, along with
a unified way to sign it across all SoCs, is more worth the effort than
trying to get poorly-written Amlogic utilities to work, along with a
fully proprietary "Trusted Firmware" (it's not that secure) boot chain.
I also forgot to point out that these tools are x86_64-only, so if you
wanted to compile U-Boot on any other architecture it wouldn't work at
all.
But this RFC patch does show how binman can be used for making all that
complex signing automatically. I appreciate the effort.
>
> Neil
>
> >
> >>
> >> [1]: https://git.vitali64.duckdns.org/misc/u-boot-kii-pro.git/log/?h=wip/spl
> >> [2]: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/plat/amlogic
> >>
> >> Cheers.
> >>
> >
> > Regards,
> > Simon
Cheers.
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Ferass El Hafidi <vitali64pmemail@protonmail.com>
To: neil.armstrong@linaro.org, Simon Glass <sjg@chromium.org>
Cc: christianshewitt@gmail.com, mark.kettenis@xs4all.nl,
u-boot@lists.denx.de, u-boot-amlogic@groups.io,
linux-amlogic@lists.infradead.org, alpernebiyasak@gmail.com,
da@lessconfused.com
Subject: Re: [PATCH v2 0/1] meson: Demonstration of using binman to produce the image
Date: Thu, 31 Aug 2023 10:25:40 +0000 [thread overview]
Message-ID: <CV6NO816M3FH.30VZXHR4KDM49@flaptop> (raw)
In-Reply-To: <d94b0cae-99cc-4f8b-9d0d-52a5858f6e33@linaro.org>
Hi Simon,
On Thu Aug 31, 2023 at 9:54 AM CEST, neil.armstrong wrote:
> > Thanks for your efforts on this. I look forward to seeing where it ends up.
I hope we can get it to at least boot!
> >> Honestly, in my opinion, including proprietary and poorly-written
> >> Amlogic utilities lacking a proper license, into U-Boot looks like a bad idea.
> >
> > With Binman, we don't really include them in U-Boot; we allow them to
> > be fetched easily so that a complete build can be produced.
Acknowledged.
> > I don't like it either, but for users it is better than doing the
> > build manually.
>
> I'll rather spend time and effort to have a fully-upstream TF-A boot chain
> for Amlogic SoC (when possible) that maintaining support for bulky closed-source
> x86-64 binary only tools. The tools aren't even officially distributed.
I agree with Neil here. I think having U-Boot SPL for Amlogic SoCs, along with
a unified way to sign it across all SoCs, is more worth the effort than
trying to get poorly-written Amlogic utilities to work, along with a
fully proprietary "Trusted Firmware" (it's not that secure) boot chain.
I also forgot to point out that these tools are x86_64-only, so if you
wanted to compile U-Boot on any other architecture it wouldn't work at
all.
But this RFC patch does show how binman can be used for making all that
complex signing automatically. I appreciate the effort.
>
> Neil
>
> >
> >>
> >> [1]: https://git.vitali64.duckdns.org/misc/u-boot-kii-pro.git/log/?h=wip/spl
> >> [2]: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/plat/amlogic
> >>
> >> Cheers.
> >>
> >
> > Regards,
> > Simon
Cheers.
next prev parent reply other threads:[~2023-08-31 10:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 17:53 [PATCH v2 0/1] meson: Demonstration of using binman to produce the image Ferass El Hafidi
2023-08-30 17:53 ` Ferass El Hafidi
2023-08-31 3:37 ` Simon Glass
2023-08-31 3:37 ` Simon Glass
2023-08-31 7:54 ` neil.armstrong
2023-08-31 7:54 ` neil.armstrong
2023-08-31 7:54 ` Neil Armstrong
2023-08-31 10:25 ` Ferass El Hafidi [this message]
2023-08-31 10:25 ` Ferass El Hafidi
-- strict thread matches above, loose matches on Subject: below --
2023-04-01 18:54 Simon Glass
2023-04-01 21:27 ` Mark Kettenis
[not found] ` <CAPnjgZ0Js43JOi3xaeY8tYuELSPXWL-PCBq1-iANLs1074MzbQ@mail.gmail.com>
2023-04-03 8:10 ` Christian Hewitt
2023-04-03 8:10 ` Christian Hewitt
2023-04-05 18:38 ` Simon Glass
2023-04-05 18:38 ` Simon Glass
2023-04-08 3:34 ` Da Xue
2023-04-08 3:34 ` Da Xue
2023-04-19 1:49 ` Simon Glass
2023-04-19 1:49 ` Simon Glass
2023-04-01 6:25 Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CV6NO816M3FH.30VZXHR4KDM49@flaptop \
--to=vitali64pmemail@protonmail.com \
--cc=alpernebiyasak@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=mark.kettenis@xs4all.nl \
--cc=neil.armstrong@linaro.org \
--cc=sjg@chromium.org \
--cc=u-boot-amlogic@groups.io \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.