From: Gary Bisson <gary.bisson@boundarydevices.com>
To: Heiko Thiery <heiko.thiery@gmail.com>
Cc: Gary Bisson <bisson.gary@gmail.com>,
Stephane Viau <stephane.viau@oss.nxp.com>,
Refik Tuzakli <tuzakli.refik@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot <buildroot@buildroot.org>,
Fabio Estevam <festevam@gmail.com>,
Xavier Roumegue <xroumegue@gmail.com>
Subject: Re: [Buildroot] [PATCH 0/3] Add support to build imx8 images using mainline uboot
Date: Tue, 7 Sep 2021 10:57:57 +0200 [thread overview]
Message-ID: <YTcplRmz8UP33lr1@p1g2> (raw)
In-Reply-To: <CAEyMn7bqZwYArZ0MV=G95dpuH0U_+YzLO+aV_ZHTDrt=wBiZwg@mail.gmail.com>
Hi Thiery,
On Tue, Sep 07, 2021 at 10:43:43AM +0200, Heiko Thiery wrote:
> Hi Gary,
>
> Am Di., 7. Sept. 2021 um 10:36 Uhr schrieb Gary Bisson
> <gary.bisson@boundarydevices.com>:
> >
> > Hi Thiery,
> >
> > On Tue, Sep 07, 2021 at 08:36:30AM +0200, Heiko Thiery wrote:
> > > Hi Fabio,
> > >
> > > Am Mo., 6. Sept. 2021 um 17:23 Uhr schrieb Fabio Estevam <festevam@gmail.com>:
> > > >
> > > > Hi Heiko,
> > > >
> > > > On Mon, Sep 6, 2021 at 10:32 AM Heiko Thiery <heiko.thiery@gmail.com> wrote:
> > > >
> > > > > What board are you exactly asking for? the nxp imx8mm evk? I have a
> > > > > tree for the kontron pitx-imx8m [1] that has an i.MX8MQ.
> > > > >
> > > > > Maybe this also answers your question ;-/
> > > > >
> > > > > [1] https://github.com/hthiery/buildroot/tree/uboot-imx
> > > >
> > > > This helps, thanks.
> >
> > I've tried this series with our U-Boot (2020.07 based) and it doesn't
> > work for me as using UBOOT_FORMAT_CUSTOM isn't sufficient as it only
> > copies the binaries selected but doesn't use it as target [1].
> >
> > So I wonder, which U-Boot version are you using? Is the flash.bin
> > created automatically when issuing 'make all'?
> > In my version of U-Boot it requires to use 'make flash.bin' otherwise it
> > simply doesn't generate flash.bin.
> >
> > I believe we would still need a new U-Boot target name [2] but I'd like
> > to understand how it worked for you
>
> Yes, when switching to binman the "make all" target will create the
> flash.bin (all output that is defined/described in binman). So in your
> case when you use the "old" u-boot way of creating this output we have
> to add a new u-boot target in buildroot.
Thanks for the quick reply. Indeed I just saw in your U-Boot tree how
the binman description was done, it's pretty neat.
So do you know if the flash.bin target is here to stay in U-Boot or is
binman to new way to go and flash.bin becomes an outdated target? I know
it's more of a U-Boot question than Buildroot but just to understand if
it even makes sense to add the target if it's going to disappear in
upcoming releases.
Regards,
Gary
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-09-07 8:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 9:42 [Buildroot] [PATCH 0/3] Add support to build imx8 images using mainline uboot Heiko Thiery
2021-09-06 9:42 ` [Buildroot] [PATCH 1/3] package/freescale-imx/firmware-imx: copy all (lp)ddr files unconditionaly Heiko Thiery
2021-09-07 8:29 ` Gary Bisson
2021-09-06 9:42 ` [Buildroot] [PATCH 2/3] boot/uboot: copy ATF bl31 binary to uboot package dir Heiko Thiery
2021-09-06 10:23 ` Michael Walle
2021-09-07 9:16 ` Heiko Thiery
2021-09-06 9:42 ` [Buildroot] [PATCH 3/3] boot/uboot: copy IMX firmware files " Heiko Thiery
2021-09-06 12:45 ` Stephane Viau (OSS)
2021-09-06 12:48 ` Fabio Estevam
2021-09-06 12:57 ` Stephane Viau (OSS)
2021-09-06 13:20 ` Heiko Thiery
2021-09-06 12:25 ` [Buildroot] [PATCH 0/3] Add support to build imx8 images using mainline uboot Fabio Estevam
2021-09-06 13:32 ` Heiko Thiery
2021-09-06 15:23 ` Fabio Estevam
2021-09-07 6:36 ` Heiko Thiery
2021-09-07 8:36 ` Gary Bisson
2021-09-07 8:43 ` Heiko Thiery
2021-09-07 8:57 ` Gary Bisson [this message]
2021-09-07 9:03 ` 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=YTcplRmz8UP33lr1@p1g2 \
--to=gary.bisson@boundarydevices.com \
--cc=bisson.gary@gmail.com \
--cc=buildroot@buildroot.org \
--cc=festevam@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=stephane.viau@oss.nxp.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tuzakli.refik@gmail.com \
--cc=xroumegue@gmail.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