From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] common: imx: Implement generic u-boot.nand target
Date: Tue, 26 Feb 2013 00:03:30 +0100 [thread overview]
Message-ID: <201302260003.30640.marex@denx.de> (raw)
In-Reply-To: <1361830537.27903.11@snotra>
Dear Scott Wood,
> On 02/25/2013 03:10:35 PM, Marek Vasut wrote:
> > Dear Scott Wood,
> >
> > > On 02/25/2013 12:19:54 PM, Marek Vasut wrote:
> > > > +$(obj)u-boot.nand: $(obj)u-boot.bin depend
> > > > + if [ "X$(CONFIG_NAND_TRG_PATH)X" = "XX" ] ;
> > > > then \
> > > > + echo "This CPU does not support u-boot.nand
> > > > target!" ; \
> > > > + exit 1
> > > > ; \
> > > > + fi
> > > > + $(MAKE) -C $(CONFIG_NAND_TRG_PATH) $(obj)u-boot.nand
> > >
> > > We already have CONFIG_SPL_TARGET. Why do we need a new mechanism
> > > specific to NAND, with ifdefs in the main Makefile?
> >
> > This board doesn't use SPL at all.
>
> So maybe we need a more general (but optional) CONFIG_BUILD_TARGET.
Can you elaborate?
> > > If we do have something specific to NAND, it should be
> >
> > u-boot-nand.bin
> >
> > > to match what nand_spl produced, and it should just be a generic
> >
> > rule
> >
> > > that links to what CONFIG_SPL_TARGET produced, if the right CONFIG
> > > symbol is set by the board config to say that this is a NAND SPL.
> >
> > Or
> >
> > > is someone going to say that they want to generate multiple
> >
> > different
> >
> > > SPL images from the same build? :-P
> >
> > I'd like to generate a bootable NAND image on mx53 and on mx23/28,
>
> From the same build, or just in general?
What do you mean by 'from the same build' ? From a build for the particular
board running the SOC=mxs .
> > thus I need generic target. And I need it flexible enough, since on
> > mx23/28 it munges u-
> > boot.sb into the resulting image while on mx53 it munges u-boot.imx
> > into the
> > resulting image.
>
> So each one would set the appropriate CONFIG_BUILD_TARGET for whatever
> needs to get built, and then something like CONFIG_NAND_IMAGE could
> hold the image name that should be linked to produce a standard
> u-boot-nand.bin output.
Yea, sounds reasonable. But why call it CONFIG_ , it can't be stored in the
board.h files, it has to be somewhere in the Makefile hierarchy.
> -Scott
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-02-25 23:03 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 18:19 [U-Boot] [PATCH 1/4] common: imx: Implement generic u-boot.nand target Marek Vasut
2013-02-25 18:19 ` [U-Boot] [PATCH 2/4] imx: Align the imximage header and payload to multiples of 4k Marek Vasut
2013-02-25 19:13 ` Benoît Thébaudeau
2013-02-25 21:07 ` Marek Vasut
2013-02-25 21:16 ` Benoît Thébaudeau
2013-02-25 18:19 ` [U-Boot] [PATCH 3/4] mx5: Add NAND clock handling Marek Vasut
2013-02-25 19:27 ` Benoît Thébaudeau
2013-02-25 18:24 ` [U-Boot] [PATCH 4/4] mx5: Add support for DENX M53EVK Marek Vasut
2013-02-25 19:33 ` Benoît Thébaudeau
2013-02-26 13:52 ` Fabio Estevam
2013-02-26 19:32 ` Fabio Estevam
2013-04-14 17:20 ` Marek Vasut
2013-04-14 19:07 ` Wolfgang Denk
2013-04-14 19:18 ` Marek Vasut
2013-02-25 18:51 ` [U-Boot] [PATCH 1/4] common: imx: Implement generic u-boot.nand target Benoît Thébaudeau
2013-02-25 21:09 ` Marek Vasut
2013-02-25 21:13 ` Benoît Thébaudeau
2013-02-26 1:02 ` [U-Boot] patch error wanxs
2013-02-25 20:10 ` [U-Boot] [PATCH 1/4] common: imx: Implement generic u-boot.nand target Scott Wood
2013-02-25 21:10 ` Marek Vasut
2013-02-25 22:15 ` Scott Wood
2013-02-25 23:03 ` Marek Vasut [this message]
2013-02-25 23:07 ` Scott Wood
2013-02-25 23:50 ` Benoît Thébaudeau
2013-02-26 7:19 ` Marek Vasut
2013-02-26 11:33 ` Benoît Thébaudeau
2013-02-27 17:33 ` Tom Rini
2013-02-28 18:50 ` Marek Vasut
2013-02-28 18:53 ` Tom Rini
2013-02-26 7:17 ` Marek Vasut
2013-02-26 23:10 ` Scott Wood
2013-02-27 22:18 ` Benoît Thébaudeau
2013-02-27 23:44 ` Tom Rini
2013-02-27 23:47 ` Benoît Thébaudeau
2013-02-28 12:18 ` Benoît Thébaudeau
2013-02-28 14:03 ` Tom Rini
2013-02-28 15:24 ` Benoît Thébaudeau
2013-02-28 16:06 ` Benoît Thébaudeau
2013-02-28 16:21 ` Tom Rini
2013-02-28 16:29 ` Benoît Thébaudeau
2013-02-28 16:42 ` Tom Rini
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=201302260003.30640.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox