From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] MAKEALL ARMv7: Use boards.cfg
Date: Sat, 6 Aug 2011 08:48:32 +0200 [thread overview]
Message-ID: <1312613312-27072-1-git-send-email-dirk.behme@gmail.com> (raw)
From: Dirk Behme <dirk.behme@googlemail.com>
Use the boards from boards.cfg for building ./MAKEALL ARMV7.
Signed-off-by: Dirk Behme <dirk.behme@googlemail.com>
---
Changes in v3: Instead of touching all ARMx boards, only update
ARMV7. Current LIST_ARMV7 builds 19 boards while -c armv7 (i.e. using
boards.cfg) builds 31 boards (including all boards from the current
LIST_ARMV7).
Changes in v2: Instead of dublicating the missing boards from
boards.cfg to MAKEALL, use the boards defined in boards.cfg
directly. See
http://lists.denx.de/pipermail/u-boot/2011-August/097858.html
MAKEALL | 23 ++---------------------
1 file changed, 2 insertions(+), 21 deletions(-)
Index: u-boot.git/MAKEALL
===================================================================
--- u-boot.git.orig/MAKEALL
+++ u-boot.git/MAKEALL
@@ -417,27 +417,8 @@ LIST_ARM11=" \
#########################################################################
## ARMV7 Systems
#########################################################################
-LIST_ARMV7=" \
- am3517_crane \
- am3517_evm \
- ca9x4_ct_vxp \
- devkit8000 \
- dig297 \
- igep0020 \
- igep0030 \
- mx51evk \
- omap3_beagle \
- omap3_overo \
- omap3_evm \
- omap3_pandora \
- omap3_sdp3430 \
- omap3_zoom1 \
- omap3_zoom2 \
- omap4_panda \
- omap4_sdp4430 \
- s5p_goni \
- smdkc100 \
-"
+
+LIST_ARMV7="$(boards_by_cpu armv7)"
#########################################################################
## AT91 Systems
next reply other threads:[~2011-08-06 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 6:48 Dirk Behme [this message]
2011-08-07 9:16 ` [U-Boot] [PATCH v3] MAKEALL ARMv7: Use boards.cfg Albert ARIBAUD
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=1312613312-27072-1-git-send-email-dirk.behme@gmail.com \
--to=dirk.behme@googlemail.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