From: Sanjeev Premi <premi@ti.com>
To: barebox@lists.infradead.org
Subject: [PATCH 3/5] ARM omap3evm: Allow building first stage bootloader
Date: Wed, 11 Jan 2012 20:27:20 +0530 [thread overview]
Message-ID: <1326293842-3063-4-git-send-email-premi@ti.com> (raw)
In-Reply-To: <s.hauer@pengutronix.de,plagnioj@jcrosoft.com,J.Kilb@phytec.de>
Enable the flag HAVE_NOSHELL to allow first stage
bootloader to be built for this board.
Signed-off-by: Sanjeev Premi <premi@ti.com>
---
Tested after creating minimal configuration based on
omap3530_beagle_xload_defconfig.
arch/arm/mach-omap/Kconfig | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap/Kconfig b/arch/arm/mach-omap/Kconfig
index 73125a7..72c6850 100644
--- a/arch/arm/mach-omap/Kconfig
+++ b/arch/arm/mach-omap/Kconfig
@@ -133,6 +133,7 @@ config MACH_OMAP3EVM
bool "Texas Instrument's OMAP3 EVM"
select MACH_HAS_LOWLEVEL_INIT
select OMAP_CLOCK_ALL
+ select HAVE_NOSHELL
select HAS_OMAP_NAND
depends on ARCH_OMAP3
help
--
1.7.0.4
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-01-11 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s.hauer@pengutronix.de,plagnioj@jcrosoft.com,J.Kilb@phytec.de>
2012-01-11 14:57 ` [PATCH 0/5] ARM omap: Some fixes and enhancements Sanjeev Premi
2012-01-11 17:32 ` Premi, Sanjeev
2012-01-11 17:52 ` Premi, Sanjeev
2012-01-11 14:57 ` [PATCH 1/5] ARM omap: Use updated config option Sanjeev Premi
2012-01-11 14:57 ` [PATCH 2/5] ARM omap3beagle: Fix incorrect base addresses Sanjeev Premi
2012-01-11 14:57 ` Sanjeev Premi [this message]
2012-01-11 14:57 ` [PATCH 4/5] ARM omap3evm: Enable HSMMC device Sanjeev Premi
2012-01-11 14:57 ` [PATCH 5/5] ARM omap: Set IFT target as MLO Sanjeev Premi
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=1326293842-3063-4-git-send-email-premi@ti.com \
--to=premi@ti.com \
--cc=barebox@lists.infradead.org \
/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