From: Fabio Estevam <festevam@gmail.com>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Heiko Thiery <heiko.thiery@gmail.com>,
ZHIZHIKIN Andrey <andrey.zhizhikin@leica-geosystems.com>,
Oliver Graute <oliver.graute@kococonnector.com>,
"sbabic@denx.de" <sbabic@denx.de>,
"peng.fan@nxp.com" <peng.fan@nxp.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
Simon Glass <sjg@chromium.org>, uboot-imx <uboot-imx@nxp.com>,
Alexandru Gagniuc <mr.nuke.me@gmail.com>,
Marek Vasut <marex@denx.de>
Subject: Re: [PATCH v1] imx: mkimage_fit_atf: replace @ with hyphen
Date: Fri, 13 Aug 2021 09:34:40 -0300 [thread overview]
Message-ID: <CAOMZO5A_L5VDE9QsOik60y78ozQq+bPkMhN6ONuv8F9zEjUDWQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ+vNU1AayntQeQ_VLC8NpNcj3HANPna9OzxUqNJHAT74e-O1g@mail.gmail.com>
Hi Tim,
[Adding Marek]
On Tue, Jul 27, 2021 at 6:53 PM Tim Harvey <tharvey@gateworks.com> wrote:
> With respect to moving to binman, I'm all for it but I'm wondering why
> other boards have elected to move from a monolithic flash.bin
> including the SPL and u-boot.itb pre-binman to post-binman where
> flash.bin is just the SPL. I'm not sure why users should be hit with a
> change like that... why are people not having binman produce a
> flash.bin that was equivalent to pre-binman?
Yes, fully agree.
Peng,
After the adoption of binman, both flash.bin and u-boot.itb need to be
flashed to the boot media.
This breaks user experience, distro integration, etc, which is not good.
Can we have binman generate a single bootable flash.bin binary (which
contains flash.bin + u-boot.itb) again
to keep compatibility and avoid breakage?
Thanks,
Fabio Estevam
>
> Best regards,
>
> Tim
next prev parent reply other threads:[~2021-08-13 12:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 12:00 [PATCH v1] imx: mkimage_fit_atf: replace @ with hyphen Oliver Graute
2021-05-05 13:30 ` ZHIZHIKIN Andrey
2021-07-27 19:17 ` Heiko Thiery
2021-07-27 21:53 ` Tim Harvey
2021-08-02 9:57 ` Peng Fan (OSS)
2021-08-08 15:48 ` Heiko Thiery
2021-08-13 12:34 ` Fabio Estevam [this message]
2021-08-13 12:52 ` Heiko Thiery
2021-08-13 13:03 ` Fabio Estevam
2021-08-13 15:12 ` Heiko Thiery
2021-08-16 6:01 ` Heiko Thiery
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=CAOMZO5A_L5VDE9QsOik60y78ozQq+bPkMhN6ONuv8F9zEjUDWQ@mail.gmail.com \
--to=festevam@gmail.com \
--cc=andrey.zhizhikin@leica-geosystems.com \
--cc=heiko.thiery@gmail.com \
--cc=marex@denx.de \
--cc=mr.nuke.me@gmail.com \
--cc=oliver.graute@kococonnector.com \
--cc=peng.fan@nxp.com \
--cc=sbabic@denx.de \
--cc=sjg@chromium.org \
--cc=tharvey@gateworks.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
/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;
as well as URLs for NNTP newsgroup(s).