public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Josh Karabin <gkarabin@vocollect.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] Support NAND and OneNAND memories on the OMAP3 EVM
Date: Tue, 26 May 2009 16:13:54 -0400	[thread overview]
Message-ID: <cover.1243367498.git.gkarabin@vocollect.com> (raw)

This patch series permits the OMAP3 EVM to select which set of NAND or
OneNAND memory related commands to use, as a function of the detected
bootstrap configuration.

In addition to the OMAP3-specific parts, it abstracts the selection of the
environment's location so that the choice can be made at run-time, not just
compile time.  It also makes it possible to disable support for compiled-in
u-boot commands.

In particular, the changes to memory types other than NAND and OneNAND will
need some scrutiny, since I don't have a good way to test some of those
systems, or even to compile them.

Josh Karabin (4):
  Support multiple CONFIG_ENV options in a single build.
  Support run-time disabling of NAND and OneNAND memories.
  Support run-time disabling of u-boot commands.
  Support NAND and OneNAND memories on the OMAP3 EVM.

 board/omap3/evm/evm.c                  |   24 +++++++++++
 board/omap3/evm/evm.h                  |    4 +-
 common/cmd_nvedit.c                    |    4 +-
 common/command.c                       |   43 +++++++++++--------
 common/env_common.c                    |   64 ++++++++++++++++++++++++++---
 common/env_dataflash.c                 |   25 ++++++++----
 common/env_eeprom.c                    |   24 +++++++----
 common/env_flash.c                     |   34 +++++++++++----
 common/env_mgdisk.c                    |   23 +++++++----
 common/env_nand.c                      |   61 ++++++++++++++++------------
 common/env_nowhere.c                   |   20 +++++++--
 common/env_nvram.c                     |   27 ++++++++----
 common/env_onenand.c                   |   28 +++++++++----
 common/env_sf.c                        |   21 ++++++---
 cpu/arm_cortexa8/omap3/mem.c           |   71 ++++++++++++++++++++------------
 drivers/mtd/nand/nand.c                |   10 ++++
 drivers/mtd/onenand/onenand_uboot.c    |    9 ++++
 include/asm-arm/arch-omap3/sys_proto.h |    2 +-
 include/configs/omap3_evm.h            |    4 ++
 include/environment.h                  |   43 +++++++++++++++++++
 include/nand.h                         |    1 +
 include/onenand_uboot.h                |    1 +
 22 files changed, 397 insertions(+), 146 deletions(-)

             reply	other threads:[~2009-05-26 20:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 20:13 Josh Karabin [this message]
2009-05-26 20:14 ` [U-Boot] [PATCH 1/4] Support multiple CONFIG_ENV options in a single build Josh Karabin
2009-05-26 21:01   ` Wolfgang Denk
2009-05-26 20:14 ` [U-Boot] [PATCH 2/4] Support run-time disabling of NAND and OneNAND memories Josh Karabin
2009-05-26 21:06   ` Wolfgang Denk
2009-05-26 20:14 ` [U-Boot] [PATCH 3/4] Support run-time disabling of u-boot commands Josh Karabin
2009-05-26 21:11   ` Wolfgang Denk
2009-05-26 20:14 ` [U-Boot] [PATCH 4/4] Support NAND and OneNAND memories on the OMAP3 EVM Josh Karabin
2009-05-26 21:14   ` Wolfgang Denk

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=cover.1243367498.git.gkarabin@vocollect.com \
    --to=gkarabin@vocollect.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