From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 03/10] mkconfig: add support for SPL CPU
Date: Wed, 6 Jun 2012 11:09:48 -0700 [thread overview]
Message-ID: <20120606180947.GD13311@nvidia.com> (raw)
In-Reply-To: <4FCF8346.2020208@wwwdotorg.org>
On Wed, Jun 06, 2012 at 09:20:22AM -0700, Stephen Warren wrote:
> On 06/05/2012 03:20 PM, Allen Martin wrote:
> > Add support for specifying a differnt CPU for main u-boot and SPL
>
> typo ^^
Got it, thanks.
> > u-boot builds. This is done by adding an optional SPL CPU after the
> > main CPU in boards.cfg as follows:
> >
> > normal_cpu:spl_cpu
> >
> > This this case CPU will be set to "normal_cpu" during the main u-boot
> > build and "spl_cpu" during the SPL build.
>
> > diff --git a/mkconfig b/mkconfig
>
> > +tmp="${cpu#*:}"
> > +if [ "$tmp" != "$cpu" ] ; then
> > + spl_cpu=$tmp
> > + cpu="${cpu%:*}"
> > +fi
>
> Neat - I wasn't aware of those variable expansion techniques.
>
> However, this script runs under /bin/sh - are they standard sh
> constructs, or are they bash-isms? I wonder if shelling out to awk or
> cut here would be more portable?
It's bash, I'll rewrite it with awk.
-Allen
--
nvpublic
next prev parent reply other threads:[~2012-06-06 18:09 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 21:20 [U-Boot] [PATCH v2 0/10] split tegra20 arm7 code into separate SPL Allen Martin
2012-06-05 21:20 ` [U-Boot] [PATCH v2 01/10] tegra20: rename tegra2 -> tegra20 Allen Martin
2012-06-06 16:11 ` Stephen Warren
2012-06-06 18:02 ` Allen Martin
2012-06-05 21:20 ` [U-Boot] [PATCH v2 02/10] tegra20: move tegra20 SoC code to arch/arm/cpu/tegra20-common Allen Martin
2012-06-06 16:16 ` Stephen Warren
2012-06-06 18:07 ` Allen Martin
2012-06-05 21:20 ` [U-Boot] [PATCH v2 03/10] mkconfig: add support for SPL CPU Allen Martin
2012-06-06 16:20 ` Stephen Warren
2012-06-06 18:09 ` Allen Martin [this message]
2012-06-05 21:20 ` [U-Boot] [PATCH v2 04/10] ARM: Fix arm720t SPL build Allen Martin
2012-06-05 21:20 ` [U-Boot] [PATCH v2 05/10] tegra20: remove timer_init from " Allen Martin
2012-06-05 21:20 ` [U-Boot] [PATCH v2 06/10] ARM: add tegra20 support to arm720t Allen Martin
2012-06-06 16:39 ` Stephen Warren
2012-06-06 18:25 ` Allen Martin
2012-06-06 19:17 ` Stephen Warren
2012-06-06 22:18 ` Allen Martin
2012-06-06 23:19 ` Stephen Warren
2012-06-05 21:20 ` [U-Boot] [PATCH v2 07/10] tegra20: add SPL config options for seaboard Allen Martin
2012-06-06 16:44 ` Stephen Warren
2012-06-06 18:40 ` Allen Martin
2012-06-07 7:15 ` Sughosh Ganu
2012-06-07 16:36 ` Stephen Warren
2012-06-07 17:04 ` Sughosh Ganu
2012-06-07 20:02 ` Stephen Warren
2012-06-05 21:20 ` [U-Boot] [PATCH v2 08/10] tegra20: add u-boot.t2 target Allen Martin
2012-06-06 16:48 ` Stephen Warren
2012-06-06 19:37 ` Allen Martin
2012-06-06 19:53 ` Tom Warren
2012-06-06 19:57 ` Stephen Warren
2012-06-06 22:00 ` Allen Martin
2012-06-07 2:02 ` Stephen Warren
2012-06-07 17:06 ` Allen Martin
2012-06-05 21:20 ` [U-Boot] [PATCH v2 09/10] tegra20: Remove CPU init code from tegra20 u-boot Allen Martin
2012-06-06 16:51 ` Stephen Warren
2012-06-06 19:42 ` Allen Martin
2012-06-05 21:20 ` [U-Boot] [PATCH v2 10/10] tegra20: Remove armv4t build flags Allen Martin
2012-06-06 16:52 ` Stephen Warren
2012-06-05 21:25 ` [U-Boot] [PATCH v2 0/10] split tegra20 arm7 code into separate SPL Tom Warren
2012-06-05 23:45 ` Allen Martin
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=20120606180947.GD13311@nvidia.com \
--to=amartin@nvidia.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