public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
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 12:33:52 +0100 (CET)	[thread overview]
Message-ID: <1636401851.120330.1361878432310.JavaMail.root@advansee.com> (raw)
In-Reply-To: <201302260819.43138.marex@denx.de>

On Tuesday, February 26, 2013 8:19:42 AM, Marek Vasut wrote:
> Dear Beno?t Th?baudeau,
> 
> > Dear Scott Wood,
> > 
> > On Tuesday, February 26, 2013 12:07:25 AM, Scott Wood wrote:
> > > On 02/25/2013 05:03:30 PM, Marek Vasut wrote:
> > > > Dear Scott Wood,
> > > > 
> > > > > So maybe we need a more general (but optional) CONFIG_BUILD_TARGET.
> > > > 
> > > > Can you elaborate?
> > > 
> > > Same as CONFIG_SPL_TARGET, but not SPL-specific.  Basically a way for a
> > > board config file to add to $(ALL-y).
> > > 
> > > > > 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.
> > > 
> > > Why can't it go in the board.h files?
> > 
> > We could do all that, but should we? As I said to Marek, I think that it's
> > a big mistake to omit the SPL here. The only other solution to get a
> > reliable boot would be the DBBT, but it's very hard to use in real life,
> > away from a production line. The SPL is really easy to enable here, and
> > it's only a matter of time before someone gets bitten by this lack of
> > reliability, so why not just do things right? The boot time and footprint
> > of an SPL would really be negligible, and it's not because other
> > implementations omit both SPL and a valid DBBT that U-Boot should do the
> > same.
> 
> I'm not against SPL, but then we're starting to drift away from the whole
> idea
> of generating u-boot-nand.bin or similar image. Being able to generate
> u-boot-
> nand.bin or u-boot-sd.bin etc ... on a per-CPU basis (since this is CPU
> specific) is the ultimate goal here, whatever is embedded in the image.

OK, I didn't know that this was your goal here. If the contents of the image do
not matter, then my u-boot-with-nand-spl.imx could be renamed into your
u-boot-nand.bin with the appropriate FCB header, and CONFIG_SPL_TARGET could be
changed to something more generic as Scott explained.

Best regards,
Beno?t

  reply	other threads:[~2013-02-26 11:33 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
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 [this message]
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=1636401851.120330.1361878432310.JavaMail.root@advansee.com \
    --to=benoit.thebaudeau@advansee.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