From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: mxs: tools: Use mkimage for BootStream generation
Date: Tue, 24 Sep 2013 17:25:31 +0200 [thread overview]
Message-ID: <201309241725.31848.marex@denx.de> (raw)
In-Reply-To: <CAP9ODKquzvZMmXWhZ_g_2h5N+3_arThMN7b-n-XSkbPnzVBThQ@mail.gmail.com>
Dear Otavio Salvador,
> On Tue, Sep 24, 2013 at 11:51 AM, Marek Vasut <marex@denx.de> wrote:
> > Dear Otavio Salvador,
> >
> >> On Tue, Sep 24, 2013 at 11:40 AM, Marek Vasut <marex@denx.de> wrote:
> >> > Now that mkimage can generate an BootStream for i.MX23 and i.MX28,
> >> > use the mkimage as a default tool to generate the BootStreams instead
> >> > of the elftosb tool. This cuts out another obscure dependency.
> >> >
> >> > Signed-off-by: Marek Vasut <marex@denx.de>
> >> > Cc: Fabio Estevam <fabio.estevam@freescale.com>
> >> > Cc: Otavio Salvador <otavio@ossystems.com.br>
> >> > Cc: Stefano Babic <sbabic@denx.de>
> >> > ---
> >> >
> >> > arch/arm/cpu/arm926ejs/mxs/Makefile | 11 +++++----
> >> > arch/arm/cpu/arm926ejs/mxs/mxsimage.mx23.cfg | 4 ++--
> >> > arch/arm/cpu/arm926ejs/mxs/mxsimage.mx28.cfg | 4 ++--
> >> > doc/README.mxs | 34
> >> > +++++++++++++++++++++++++--- 4 files changed, 41 insertions(+), 12
> >> > deletions(-)
> >> >
> >> > diff --git a/arch/arm/cpu/arm926ejs/mxs/Makefile
> >> > b/arch/arm/cpu/arm926ejs/mxs/Makefile index 3d66892..3e9cbdb 100644
> >> > --- a/arch/arm/cpu/arm926ejs/mxs/Makefile
> >> > +++ b/arch/arm/cpu/arm926ejs/mxs/Makefile
> >> > @@ -25,14 +25,15 @@ $(LIB): $(OBJS)
> >> >
> >> > $(call cmd_link_o_target, $(OBJS))
> >> >
> >> > # Specify the target for use in elftosb call
> >> >
> >> > -ELFTOSB_TARGET-$(CONFIG_MX23) = imx23
> >> > -ELFTOSB_TARGET-$(CONFIG_MX28) = imx28
> >> > +ELFTOSB_TARGET-$(CONFIG_MX23) = mx23
> >> > +ELFTOSB_TARGET-$(CONFIG_MX28) = mx28
> >>
> >> Uh?! this seems wrong.
> >
> > Why ?
>
> elftosb uses the former way; in case you might change the target var for:
>
> MXSIMAGE_TARGET
>
> So this does not cause confusion.
OK. Next time you could include such vital information in your first email.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-09-24 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 14:40 [U-Boot] [PATCH] ARM: mxs: tools: Use mkimage for BootStream generation Marek Vasut
2013-09-24 14:41 ` Marek Vasut
2013-09-24 14:47 ` Otavio Salvador
2013-09-24 14:51 ` Marek Vasut
2013-09-24 14:58 ` Otavio Salvador
2013-09-24 15:25 ` Marek Vasut [this message]
2013-09-24 16:09 ` Otavio Salvador
2013-09-24 16:31 ` Marek Vasut
2013-09-24 16:30 ` Marek Vasut
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=201309241725.31848.marex@denx.de \
--to=marex@denx.de \
--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.