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 6/9] tegra: enable SPL build for seaboard
Date: Fri, 18 May 2012 15:24:40 -0700	[thread overview]
Message-ID: <20120518222440.GC30009@nvidia.com> (raw)
In-Reply-To: <4FB1E460.7010405@wwwdotorg.org>

On Mon, May 14, 2012 at 10:06:40PM -0700, Stephen Warren wrote:
> On 05/10/2012 01:02 AM, Allen Martin wrote:
> > Signed-off-by: Allen Martin <amartin@nvidia.com>
> 
> > diff --git a/boards.cfg b/boards.cfg
> 
> > -seaboard                     arm         armv7       seaboard            nvidia         tegra2
> > +seaboard                     arm         armv7:arm720t seaboard          nvidia         tegra2
> 
> Hmmm. We'll have to duplicate this change for all boards. Is there some
> way to do set up the SPL CPU for all Tegra boards so we don't have to do
> that?

I would have to think what that would look like.  The boards.cfg file
has one entry per board and doesn't really have any place to store
information on groups of boards or any type of per vendor or per
architecture settings.  This decision on the CPU needs to be made at
mkconfig time or else I wouldn't have touched boards.cfg format at all
and stuck it in some tegra specific config file or Makefile.  I can't
see any way to do what you're asking without making the change even
more invasive.

> > diff --git a/include/configs/seaboard.h b/include/configs/seaboard.h
> 
> > +#ifndef CONFIG_SPL_BUILD
> 
> And every Tegra board's config header will have to ifdef a bunch of
> stuff out for SPL.

I'll take a pass at trying to pull some of that out into a common
header. 


> Perhaps we can just create a new tegra_spl board for the SPL rather than
> having an SPL variant for each board. Still, I don't know how we'd
> represent the UART differences if we did that though.

I tossed out that idea as part of the discussion about using a
separate toolchain for the SPL, but Wolfgang shot it down:

http://lists.denx.de/pipermail/u-boot/2012-April/122248.html

-Allen
-- 
nvpublic

  reply	other threads:[~2012-05-18 22:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10  7:02 [U-Boot] [PATCH 0/9] split tegra arm7 code into separate SPL Allen Martin
2012-05-10  7:02 ` [U-Boot] [PATCH 1/9] tegra2: move tegra2 SoC code to arch/arm/cpu/tegra2-common Allen Martin
2012-05-10  7:02 ` [U-Boot] [PATCH 2/9] mkconfig: add support for SPL CPU Allen Martin
2012-05-10  7:02 ` [U-Boot] [PATCH 3/9] ARM: Fix arm720t SPL build Allen Martin
2012-05-10  7:02 ` [U-Boot] [PATCH 4/9] tegra: Add SPL build support to tegra boards Allen Martin
2012-05-15  4:55   ` Stephen Warren
2012-05-18 22:42     ` Allen Martin
2012-05-10  7:02 ` [U-Boot] [PATCH 5/9] ARM: add tegra support to arm720t Allen Martin
2012-05-15  5:03   ` Stephen Warren
2012-05-18 22:37     ` Allen Martin
2012-05-22 17:10       ` Stephen Warren
2012-05-22 19:14         ` Allen Martin
2012-05-10  7:02 ` [U-Boot] [PATCH 6/9] tegra: enable SPL build for seaboard Allen Martin
2012-05-15  5:06   ` Stephen Warren
2012-05-18 22:24     ` Allen Martin [this message]
2012-05-22 17:07       ` Stephen Warren
2012-05-22 19:02         ` Allen Martin
2012-05-10  7:02 ` [U-Boot] [PATCH 7/9] tegra: add u-boot.t2 target Allen Martin
2012-05-15  5:08   ` Stephen Warren
2012-05-18 22:14     ` Allen Martin
2012-05-10  7:02 ` [U-Boot] [PATCH 8/9] tegra2: Remove CPU init code from tegra2 u-boot Allen Martin
2012-05-10  7:02 ` [U-Boot] [PATCH 9/9] tegra2: Remove USE_PRIVATE_LIBGCC and armv4t build flags Allen Martin
2012-05-15  5:11   ` Stephen Warren
2012-05-18 22:13     ` 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=20120518222440.GC30009@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