From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: Simon Glass <sjg@chromium.org>
Cc: neil.armstrong@linaro.org, u-boot-amlogic@groups.io,
u-boot@lists.denx.de, alpernebiyasak@gmail.com,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v2 1/1] RFC: Move Odroid-C2 to use binman to produce the image
Date: Thu, 06 Apr 2023 00:06:26 +0200 [thread overview]
Message-ID: <871qkyasrh.fsf@bloch.sibelius.xs4all.nl> (raw)
In-Reply-To: <CAPnjgZ2TNR2R+20WH_iaz0S-k8kwOSZcxFU_0_NnCfmFJo_rcA@mail.gmail.com> (message from Simon Glass on Thu, 6 Apr 2023 06:38:19 +1200)
> From: Simon Glass <sjg@chromium.org>
> Date: Thu, 6 Apr 2023 06:38:19 +1200
>
> Hi Neil,
>
> On Mon, 3 Apr 2023 at 19:31, Neil Armstrong <neil.armstrong@linaro.org> wrote:
> >
> > Hi Simon !
> >
> > On 01/04/2023 20:54, Simon Glass wrote:
> > > This shows how binman can be used to replace the long and complicated
> > > instructions with an automated build. It is still complicated to read
> > > but users don't have to worry about the details.
> > >
> > > It needs some tidying up and only supports Odroid-C2 at present.
> >
> > Like the v1, the work is really nice, but the dependency on vendor
> > binary-only tools doesn't make feel confident about merging this.
>
> So long as we can download it from somewhere, that is OK, or at least
> better than nothing. Is there a standard download location for the
> tools?
The tools are Linux x86-64 only, so...
> > We have open source implementation for all boards, but still dependeing on
> > tools we must manually build isn't optimal.
> >
> > What would be optimal would be to re-implement those tools into python
> > libraries and merge them into the u-boot tree then use them from binman.
>
> Or C, perhaps? Then binman can call the tools.
...this would be preferable.
> > But this could be merged as first step, them the python libaray could be
> > modified to support the binary tools & a probable python re-implementation.
>
> Yes I think it would good to get this in, even if it only supports a
> few boards. It is easy to add more, when possible.
>
> Regards,
> SImon
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-04-05 22:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 18:54 [PATCH v2 0/1] meson: Demonstration of using binman to produce the image Simon Glass
2023-04-01 18:54 ` [PATCH v2 1/1] RFC: Move Odroid-C2 to use " Simon Glass
2023-04-01 20:53 ` Steev Klimaszewski
2023-04-03 7:31 ` Neil Armstrong
2023-04-05 18:38 ` Simon Glass
2023-04-05 22:06 ` Mark Kettenis [this message]
2023-04-06 7:44 ` neil.armstrong
2023-04-01 21:27 ` [PATCH v2 0/1] meson: Demonstration of using " Mark Kettenis
[not found] ` <CAPnjgZ0Js43JOi3xaeY8tYuELSPXWL-PCBq1-iANLs1074MzbQ@mail.gmail.com>
2023-04-03 8:10 ` Christian Hewitt
2023-04-05 18:38 ` Simon Glass
2023-04-08 3:34 ` Da Xue
2023-04-19 1:49 ` 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=871qkyasrh.fsf@bloch.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=alpernebiyasak@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox