From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 00/26] spl: Support loading a FIT image containing U-Boot
Date: Tue, 16 Feb 2016 20:34:59 +0900 [thread overview]
Message-ID: <CAK7LNARoFApxsiEw0Qtqw_s4dbN9TWLjrJ8c0zt69gjnnrdeWg@mail.gmail.com> (raw)
In-Reply-To: <1453999186-18747-1-git-send-email-sjg@chromium.org>
Hi Simon,
2016-01-29 1:39 GMT+09:00 Simon Glass <sjg@chromium.org>:
> We need a way to support more than one board per binary in U-Boot with
> device tree. Various methods have been discussed. The one that seems to make
> the most sense is to adjust SPL so that it can load a FIT which contains
> U-Boot and several device tree binaries. This is how things with with Linux:
> load a FIT and select the correct device tree to pass to Linux.
I've just skimmed over the git-logs, but I am confused.
Please makes it clearer why this is useful.
In your way, how SPL is handled?
SPL is much more board-specific than U-Boot proper.
So, I assume SPL would remain as a per-board image
even after achieving one U-Boot proper for multi-boards.
Let's say we want to support Board-A, Board-B, Board-C with one U-Boot proper.
The U-Boot proper + FIT (including DTB-A, DTB-B, DTB-C) would be
generated by one-shot
and by one defconfig.
But, we would still have to do
make board_a_defconfig && make
make board_b_defconfig && make
make board_c_defconfig && make
to generate SPL for each of the three.
Is this correct?
Supposing my guess is correct, this series would not contribute
to decreasing the number of defconfig files.
Please explain which problem you are solving with this series.
--
Best Regards
Masahiro Yamada
WARNING: multiple messages have this Message-ID (diff)
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Simon Glass <sjg@chromium.org>
Cc: Tom Rini <trini@konsulko.com>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Joe Hershberger <joe.hershberger@ni.com>,
Jerry Van Baren <vanbaren@cideas.com>,
Ian Campbell <ijc+uboot@hellion.org.uk>,
Devicetree Compiler <devicetree-compiler@vger.kernel.org>
Subject: Re: [PATCH 00/26] spl: Support loading a FIT image containing U-Boot
Date: Tue, 16 Feb 2016 20:34:59 +0900 [thread overview]
Message-ID: <CAK7LNARoFApxsiEw0Qtqw_s4dbN9TWLjrJ8c0zt69gjnnrdeWg@mail.gmail.com> (raw)
In-Reply-To: <1453999186-18747-1-git-send-email-sjg@chromium.org>
Hi Simon,
2016-01-29 1:39 GMT+09:00 Simon Glass <sjg@chromium.org>:
> We need a way to support more than one board per binary in U-Boot with
> device tree. Various methods have been discussed. The one that seems to make
> the most sense is to adjust SPL so that it can load a FIT which contains
> U-Boot and several device tree binaries. This is how things with with Linux:
> load a FIT and select the correct device tree to pass to Linux.
I've just skimmed over the git-logs, but I am confused.
Please makes it clearer why this is useful.
In your way, how SPL is handled?
SPL is much more board-specific than U-Boot proper.
So, I assume SPL would remain as a per-board image
even after achieving one U-Boot proper for multi-boards.
Let's say we want to support Board-A, Board-B, Board-C with one U-Boot proper.
The U-Boot proper + FIT (including DTB-A, DTB-B, DTB-C) would be
generated by one-shot
and by one defconfig.
But, we would still have to do
make board_a_defconfig && make
make board_b_defconfig && make
make board_c_defconfig && make
to generate SPL for each of the three.
Is this correct?
Supposing my guess is correct, this series would not contribute
to decreasing the number of defconfig files.
Please explain which problem you are solving with this series.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2016-02-16 11:34 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 16:39 [U-Boot] [PATCH 00/26] spl: Support loading a FIT image containing U-Boot Simon Glass
2016-01-28 16:39 ` Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 01/26] mkimage: Move argument processing into its own function Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 02/26] mkimage: Convert to use getopt() Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 03/26] mkimage: Sort the option processing code by option Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 04/26] mkimage: Move usage() up to the top Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 05/26] mkimage: Show an error message when usage() is called Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 06/26] mkimage: Make 'params' static Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 07/26] libfdt: Add a function to write a property placeholder Simon Glass
2016-01-28 16:39 ` Simon Glass
2016-01-29 5:29 ` [U-Boot] " David Gibson
2016-01-29 5:29 ` David Gibson
2016-01-29 18:23 ` [U-Boot] " Simon Glass
2016-01-29 18:23 ` Simon Glass
2016-01-31 9:55 ` [U-Boot] " David Gibson
2016-01-31 9:55 ` David Gibson
2016-01-28 16:39 ` [U-Boot] [PATCH 08/26] Correct defconfig ordering Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 09/26] Move CONFIG_OF_LIBFDT to Kconfig Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 10/26] Kconfig: Move CONFIG_FIT and CONFIG_OF_*_SETUP " Simon Glass
2016-01-29 5:52 ` Heiko Schocher
2016-01-28 16:39 ` [U-Boot] [PATCH 11/26] fdt: Adjust DEFAULT_DEVICE_TREE to device on OF_CONTROL Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 12/26] fdt: Allow libfdt to be used in SPL Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 13/26] sunxi: Display the board model on start-up Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 14/26] tools: Include fdt_sw.o in libfdt for mkimage Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 15/26] mkimage: Allow a FIT to include an image of any type Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 16/26] tools: Add a function to obtain the size of a file Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 17/26] image: Add functions to obtain short names Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 18/26] mkimage: Support automatic creating of a FIT without a .its Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 19/26] mkimage: Support adding device tree files to a FIT Simon Glass
2016-02-11 16:36 ` Tom Rini
2016-02-12 15:54 ` Simon Glass
2016-02-12 16:03 ` Tom Rini
2016-01-28 16:39 ` [U-Boot] [PATCH 20/26] mkimage: Support placing data outside the FIT Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 21/26] mkimage: Bring data into the FIT before processing Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 22/26] spl: Add a way for boards to select which device tree to load Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 23/26] spl: Add an option to load a FIT containing U-Boot Simon Glass
2016-02-04 15:00 ` Stefano Babic
2016-02-22 4:46 ` Simon Glass
2016-02-22 6:45 ` Stefano Babic
2016-01-28 16:39 ` [U-Boot] [PATCH 24/26] spl: Add a way to specify a list of device trees to include Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 25/26] spl: Support loading a FIT from MMC Simon Glass
2016-01-28 16:39 ` [U-Boot] [PATCH 26/26] RFC: sunxi: Enable SPL FIT support Simon Glass
2016-02-16 11:34 ` Masahiro Yamada [this message]
2016-02-16 11:34 ` [PATCH 00/26] spl: Support loading a FIT image containing U-Boot Masahiro Yamada
2016-02-16 12:17 ` [U-Boot] " Tom Rini
2016-02-16 12:17 ` Tom Rini
2016-02-16 12:30 ` Masahiro Yamada
2016-02-16 12:30 ` Masahiro Yamada
2016-02-16 13:33 ` Tom Rini
2016-02-16 13:33 ` Tom Rini
2016-02-17 11:00 ` Belisko Marek
2016-02-17 11:00 ` Belisko Marek
2016-02-19 20:55 ` Simon Glass
2016-02-19 20:55 ` Simon Glass
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=CAK7LNARoFApxsiEw0Qtqw_s4dbN9TWLjrJ8c0zt69gjnnrdeWg@mail.gmail.com \
--to=yamada.masahiro@socionext.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 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.