public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/8 v2] Introduce the Tertiary Program loader
Date: Mon, 24 Jan 2011 23:09:25 +0100	[thread overview]
Message-ID: <20110124220925.CD3B6CD1385@gemini.denx.de> (raw)
In-Reply-To: <1295906076.2051.127.camel@haiying-laptop>

Dear Haiying Wang,

In message <1295906076.2051.127.camel@haiying-laptop> you wrote:
>
> > What I do not understand is what the TPL_BOOT variable in the
> > Makefile is good for.  I cannot understand the current use.
> 
> Well, it was used to generate the tpl image under tpl/ directory. Maybe TPL_BOOT is a bad name here, I just thought it was too simple to use TPL. 

It's not the name.  But you use it ina few places here, buth then hard
encode "tpl" in a number of other paces there.  Which means that you
cannot change TPL_BOOT to any other value, or building would break.
So why do we need this variable?

> > > > > +$(TPL_BOOT):	$(TIMESTAMP_FILE) $(VERSION_FILE) depend
> > > > > +		$(MAKE) -C tpl/board/$(BOARDDIR) all
> > > > 
> > > > Assume CONFIG_TPL_U_BOOT is not defined, then TPL_BOOT is not defined,
> > > > and this rule will probably cause a build error, doesn't it?
> > > No, I don't think there is a build error.
> > 
> > WEell, if CONFIG_TPL_U_BOOT is not 'y', then TPL_BOOT is not
> > defined, which results in this make rule:
> > 
> > 	: $(TIMESTAMP_FILE) $(VERSION_FILE) depend
> > 		$(MAKE) -C tpl/board/$(BOARDDIR) all
> > 
> > i. e. there would be no target name befoe the semicolon.
> If TPL_BOOT here is not defined, the reset(after semicolon) will not be executed, just like NAND_SPL and ONENAND_IPL etc. 

Sorry, I cannot follow - which reset? which semicolon?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Quantum Mechanics is God's version of "Trust me."

  reply	other threads:[~2011-01-24 22:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 15:35 [U-Boot] [PATCH 0/8 v2] Add support to tpl boot and p1021mds board Haiying.Wang at freescale.com
2010-12-01 15:35 ` [U-Boot] [PATCH 1/8] powerpc/85xx: do not reloc l2srbar if CONFIG_FLASH_BASE is not defined Haiying.Wang at freescale.com
2010-12-01 16:01   ` Kumar Gala
2010-12-01 15:35 ` [U-Boot] [PATCH 2/8] 8xxx/ddr: add support to only compute the ddr sdram size Haiying.Wang at freescale.com
2011-01-14 16:29   ` Kumar Gala
2010-12-01 15:35 ` [U-Boot] [PATCH 3/8 v2] Introduce the Tertiary Program loader Haiying.Wang at freescale.com
2011-01-21  8:14   ` Kumar Gala
2011-01-22 22:05     ` Wolfgang Denk
2011-01-22 22:04   ` Wolfgang Denk
2011-01-24  4:21     ` Haiying Wang
2011-01-24 12:49       ` Wolfgang Denk
2011-01-24 19:38         ` Scott Wood
2011-01-24 20:08           ` Wolfgang Denk
2011-01-24 21:54         ` Haiying Wang
2011-01-24 22:09           ` Wolfgang Denk [this message]
2011-01-24 22:17             ` Haiying Wang
2011-01-24 22:29               ` Wolfgang Denk
2011-01-24 23:34                 ` Scott Wood
2011-01-26 21:07                 ` Haiying Wang
2011-01-26 21:34                   ` Wolfgang Denk

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=20110124220925.CD3B6CD1385@gemini.denx.de \
    --to=wd@denx.de \
    --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