From: Oliver Graute <oliver.graute@gmail.com>
To: Tim Harvey <tharvey@gateworks.com>
Cc: ZHIZHIKIN Andrey <andrey.zhizhikin@leica-geosystems.com>,
u-boot <u-boot@lists.denx.de>, Stefano Babic <sbabic@denx.de>,
Fabio Estevam <festevam@gmail.com>,
Schrempf Frieder <frieder.schrempf@kontron.de>,
Adam Ford <aford173@gmail.com>,
Marcel Ziswiler <marcel@ziswiler.com>,
Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: mkimage_fit_atf.sh: not found
Date: Fri, 7 Jan 2022 13:22:41 +0100 [thread overview]
Message-ID: <20220107122241.GA10212@optiplex> (raw)
In-Reply-To: <CAJ+vNU3jwO_P8Ngmj-zM2P2dj0QXSW6AK5LziJVe9C2F-Y6MtQ@mail.gmail.com>
> That would still leave the following boards broken as nobody has
> submitted binman patches for them. These are both maintained by Oliver
> Graute (added to cc):
> imx8qm_rom7720_a1_4G_defconfig
> cgtqmx8_defconfig
I will look at this. So far I don't know very much about binman. So Can
you point me to similar patches as examples? I can work on this in the
next few days, perhaps I need some hints for this.
> I believe Stefano is not currently available and I'm not sure when he
> is back to merge the pending binman conversion series. Additionally
> some of these series may need to be rebased (I know I had to do that
> twice because of things being moved to Kconfig)
Best regards,
Oliver
next prev parent reply other threads:[~2022-01-07 12:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 22:48 mkimage_fit_atf.sh: not found Tim Harvey
2022-01-04 22:54 ` Fabio Estevam
2022-01-05 13:16 ` Tom Rini
2022-01-05 11:34 ` ZHIZHIKIN Andrey
2022-01-05 19:08 ` Tim Harvey
2022-01-05 21:51 ` Marcel Ziswiler
2022-01-05 22:04 ` Tom Rini
2022-01-05 22:07 ` Marcel Ziswiler
2022-01-05 22:09 ` Tom Rini
2022-01-06 10:07 ` ZHIZHIKIN Andrey
2022-01-06 17:10 ` Tim Harvey
2022-01-06 18:59 ` Tom Rini
2022-01-06 19:05 ` ZHIZHIKIN Andrey
2022-01-06 20:43 ` Heiko Thiery
2022-01-07 1:27 ` Simon Glass
2022-01-07 12:22 ` Oliver Graute [this message]
2022-01-07 12:57 ` Adam Ford
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=20220107122241.GA10212@optiplex \
--to=oliver.graute@gmail.com \
--cc=aford173@gmail.com \
--cc=andrey.zhizhikin@leica-geosystems.com \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=jagan@amarulasolutions.com \
--cc=marcel@ziswiler.com \
--cc=sbabic@denx.de \
--cc=tharvey@gateworks.com \
--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