From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/6] omap3evm: Clean-up and add new configurations
Date: Tue, 18 Oct 2011 22:25:08 +0200 [thread overview]
Message-ID: <4E9DE0A4.2080306@aribaud.net> (raw)
In-Reply-To: <1317381541-2137-1-git-send-email-premi@ti.com>
(copying Sandeep)
Hi Sanjeev,
Le 30/09/2011 13:18, Sanjeev Premi a ?crit :
> At the base level, this patchset does following:
> - Extract common/generic configurations from
> omap3_evm_config.h to create omap3_evm_common_config.h
>
> - Add new config targets that build much smaller u-boot
> customized for the boot devices - MMC/SD or NAND.
>
> In the process, config options were re-organized to bring
> similar options together along with general clean-up.
>
> Specially, configs in this format
> #define CONFIG_FEAT_XYZ 1
> were changed to
> #define CONFIG_FEAT_XYZ
>
> The patch for regoranizing the config options and splitting
> them appear to be quite big changes... not easy to compare.
> These patches were created after squasing many incremental
> commits. These commits (before squash) are available in the
> pastebin for reference (as indicated in respective patches).
>
> An earlier version of patchset was discussed on this list
> almost an year ago. However, rework got delayed for various
> reasons.
> [1] http://marc.info/?l=u-boot&m=128828487429161&w=2
> [2] http://marc.info/?l=u-boot&m=128818733126234&w=2
>
> This patchset was created against u-boot-ti/next branch
> assuming that following patch has been applied:
> http://marc.info/?l=u-boot&m=131713568506472&w=2
>
> Sanjeev Premi (6):
> omap3evm: Reorder related config options
> omap3evm: Prepare to split configuration
> omap3evm: move common config options to new file
> omap3evm: Add (quick) configuration for MMC/SD only
> omap3evm: Add (quick) configuration for NAND only
> omap3evm: fix errors caused by multiple definitions
>
> boards.cfg | 2 +
> include/configs/omap3_evm.h | 336 ++++++--------------------------
> include/configs/omap3_evm_common.h | 292 +++++++++++++++++++++++++++
> include/configs/omap3_evm_quick_mmc.h | 91 +++++++++
> include/configs/omap3_evm_quick_nand.h | 78 ++++++++
> 5 files changed, 521 insertions(+), 278 deletions(-)
> create mode 100644 include/configs/omap3_evm_common.h
> create mode 100644 include/configs/omap3_evm_quick_mmc.h
> create mode 100644 include/configs/omap3_evm_quick_nand.h
Sandeep, does this go through your TI tree?
Amicalement,
--
Albert.
prev parent reply other threads:[~2011-10-18 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 11:18 [U-Boot] [PATCH 0/6] omap3evm: Clean-up and add new configurations Sanjeev Premi
2011-09-30 11:18 ` [U-Boot] [PATCH 1/6] omap3evm: Reorder related config options Sanjeev Premi
2011-09-30 11:18 ` [U-Boot] [PATCH 2/6] omap3evm: Prepare to split configuration Sanjeev Premi
2011-09-30 11:18 ` [U-Boot] [PATCH 3/6] omap3evm: move common config options to new file Sanjeev Premi
2011-09-30 11:18 ` [U-Boot] [PATCH 4/6] omap3evm: Add (quick) configuration for MMC/SD only Sanjeev Premi
2011-09-30 11:19 ` [U-Boot] [PATCH 5/6] omap3evm: Add (quick) configuration for NAND only Sanjeev Premi
2011-09-30 11:19 ` [U-Boot] [PATCH 6/6] omap3evm: fix errors caused by multiple definitions Sanjeev Premi
2011-10-18 20:25 ` Albert ARIBAUD [this message]
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=4E9DE0A4.2080306@aribaud.net \
--to=albert.u.boot@aribaud.net \
--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