From: Sanjeev Premi <premi@ti.com>
To: barebox@lists.infradead.org
Subject: [PATCH 0/5] ARM omap: Some fixes and enhancements
Date: Wed, 11 Jan 2012 20:27:17 +0530 [thread overview]
Message-ID: <1326293842-3063-1-git-send-email-premi@ti.com> (raw)
In-Reply-To: <s.hauer@pengutronix.de,plagnioj@jcrosoft.com,J.Kilb@phytec.de>
First two patches in this series are fixes to problems in the
existing code.
Next two patches enable specific features on the OMAP3EVM.
The last patch is an enhancement to avoid manual copy each
time barebox is built as the primary bootloader i.e. in the
xload configuration.
Sanjeev Premi (5):
ARM omap: Use updated config option
ARM omap3beagle: Fix incorrect base addresses
ARM omap3evm: Allow building first stage bootloader
ARM omap3evm: Enable HSMMC device
ARM omap: Set IFT target as MLO
arch/arm/Makefile | 5 +++--
arch/arm/boards/omap/board-beagle.c | 10 +++++-----
arch/arm/boards/omap/board-omap3evm.c | 7 ++++++-
arch/arm/boards/omap/board-sdp343x.c | 2 +-
arch/arm/boards/phycard-a-l1/pca-a-l1.c | 2 +-
arch/arm/mach-omap/Kconfig | 1 +
6 files changed, 17 insertions(+), 10 deletions(-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next 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 ` Sanjeev Premi [this message]
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 ` [PATCH 3/5] ARM omap3evm: Allow building first stage bootloader Sanjeev Premi
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-1-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