public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mkconfig: add support for SPL CPU
Date: Wed, 15 Aug 2012 14:47:12 -0700	[thread overview]
Message-ID: <20120815214712.GF4086@nvidia.com> (raw)
In-Reply-To: <20120809203819.240D120401A@gemini.denx.de>

On Thu, Aug 09, 2012 at 01:38:19PM -0700, Wolfgang Denk wrote:
> Dear Allen Martin,
> 
> In message <1334858337-2853-1-git-send-email-amartin@nvidia.com> you wrote:
> > Add support for specifying a differnt CPU for main u-boot and SPL
> > 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.
> > 
> > Signed-off-by: Allen Martin <amartin@nvidia.com>
> > ---
> > This is part of my patch series to move all armv4t code out of tegra
> > u-boot to an SPL.  I haven't heard any suggestions on how to resolve
> > having a different CPU for the SPL build, so this is my suggestion
> > as a possible solution.
> > 
> >  boards.cfg     |    5 +++++
> >  doc/README.SPL |   12 ++++++++++++
> >  mkconfig       |   15 ++++++++++++++-
> >  3 files changed, 31 insertions(+), 1 deletions(-)
> 
> Applied, thanks.
> 

Thanks.  There's a newer version of this patch that we've been
carrying in the tegra tree.  Tom I'll need to rebase that patch on
top of this or they will collide the next time tegra merges up.

-Allen
-- 
nvpublic

      reply	other threads:[~2012-08-15 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 17:58 [U-Boot] [PATCH] mkconfig: add support for SPL CPU Allen Martin
2012-08-09 20:38 ` Wolfgang Denk
2012-08-15 21:47   ` Allen Martin [this message]

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=20120815214712.GF4086@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