From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Switching CPU between SPL and non-SPL build
Date: Mon, 16 Apr 2012 23:46:59 -0700 [thread overview]
Message-ID: <20120417064659.GA14997@nvidia.com> (raw)
Changing the subject line since this thread isn't really about
toolchains any more.
> > The problem I'm having with the SPL build is that a single entry in
> > boards.cfg can have exactly one architecture and CPU model. So
>
> But you can define any tye of CONFIG_ settings, both in boards.cfg and
> in your board config file.
>
> > there's no easy way to have the SPL build compile from arm720t and
> > the non SPL build compile from armv7. So I either have to have two
>
> What would prevent you from extending the Makefiles to set build
> options depending on CONFIG_ settings from your board configuration?
What I really need is the ability to change "CPU" between SPL and non
SPL build. This gets set too early for the board config file to
override. What I really need is something like this in the generated
include/config.mk:
ARCH = arm
ifeq ($(CONFIG_SPL_BUILD),y)
CPU = arm720t
else
CPU = armv7
endif
BOARD = seaboard
VENDOR = nvidia
SOC = tegra2
As an experiment I tried this, and it seems to do what I want. I
don't see a clean way to do this without it being a hack or really
intrusive though.
-Allen
nvpublic
reply other threads:[~2012-04-17 6:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120417064659.GA14997@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