public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Luka Perkov <uboot@lukaperkov.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] kwboot: Boot Marvell Kirkwood SoCs over a serial link.
Date: Wed, 25 Apr 2012 19:43:55 +0200	[thread overview]
Message-ID: <20120425174355.GA1087@w500.lan> (raw)
In-Reply-To: <20120425123407.E05DA204AE3@gemini.denx.de>

Hi Daniel,

On Wed, Apr 25, 2012 at 02:34:07PM +0200, Wolfgang Denk wrote:
> In message <1335325799.8304.15.camel@ramone> you wrote:
> >
> > > Why not use something like:
> > > 
> > > BIN_FILES-$(CONFIG_KIRKWOOD) += kwboot$(SFX)
> > 
> > Huh?
> > 
> > I don't know u-boot's build system very well, but normally CONFIG items
> > are employed to keep the target lean. Where the best you could ask from
> > down-config'd host toolset build would be to not accidentally miss sth?
> > This is all host code.
> > 
> > Is building that conditionally really best current practice? If so,
> > yeah, we sure can change that.
> > 
> > But would appreciate a clarification.
> 
> It makes no sense to build this tool on systems that will have no use
> for it - say, on Power architecture.  It only costs build time.

This is what I was talking about:

diff --git a/tools/Makefile b/tools/Makefile
index 8993fdd..8097d95 100644
--- a/tools/Makefile
+++ b/tools/Makefile
@@ -72,6 +72,7 @@ BIN_FILES-$(CONFIG_SMDK5250) += mksmdk5250spl$(SFX)
 BIN_FILES-$(CONFIG_MX28) += mxsboot$(SFX)
 BIN_FILES-$(CONFIG_NETCONSOLE) += ncb$(SFX)
 BIN_FILES-$(CONFIG_SHA1_CHECK_UB_IMG) += ubsha1$(SFX)
+BIN_FILES-$(CONFIG_KIRKWOOD) += kwboot$(SFX)
 
 # Source files which exist outside the tools directory
 EXT_OBJ_FILES-$(CONFIG_BUILD_ENVCRC) += common/env_embedded.o
@@ -101,6 +102,7 @@ OBJ_FILES-$(CONFIG_NETCONSOLE) += ncb.o
 NOPED_OBJ_FILES-y += os_support.o
 OBJ_FILES-$(CONFIG_SHA1_CHECK_UB_IMG) += ubsha1.o
 NOPED_OBJ_FILES-y += ublimage.o
+OBJ_FILES-$(CONFIG_KIRKWOOD) += kwboot.o
 
 # Don't build by default
 #ifeq ($(ARCH),ppc)
@@ -234,6 +236,10 @@ $(obj)ncb$(SFX):	$(obj)ncb.o
 $(obj)ubsha1$(SFX):	$(obj)os_support.o $(obj)sha1.o $(obj)ubsha1.o
 	$(HOSTCC) $(HOSTCFLAGS) $(HOSTLDFLAGS) -o $@ $^
 
+$(obj)kwboot$(SFX): $(obj)kwboot.o
+	$(HOSTCC) $(HOSTCFLAGS) $(HOSTLDFLAGS) -o $@ $^
+	$(HOSTSTRIP) $@
+
 # Some of the tool objects need to be accessed from outside the tools directory
 $(obj)%.o: $(SRCTREE)/common/%.c
 	$(HOSTCC) -g $(HOSTCFLAGS_NOPED) -c -o $@ $<

That worked for me. Please test this, merge it and resend patch v2.

When sending patch v2 please put me in CC because I don't look@the
mailing list regularly...

Regards,
Luka

  reply	other threads:[~2012-04-25 17:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22 20:55 [U-Boot] [PATCH] kwboot: Boot Marvell Kirkwood SoCs over a serial link Daniel Stodden
2012-04-23 20:59 ` Wolfgang Denk
2012-04-24  6:07   ` Daniel Stodden
2012-04-24  6:07     ` Daniel Stodden
2012-04-24 20:28       ` Luka Perkov
2012-04-24 23:31         ` Daniel Stodden
2012-04-25  0:08       ` Luka Perkov
2012-04-25  3:49         ` Daniel Stodden
2012-04-25 12:34           ` Wolfgang Denk
2012-04-25 17:43             ` Luka Perkov [this message]
2012-04-25  8:14       ` Prafulla Wadaskar

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=20120425174355.GA1087@w500.lan \
    --to=uboot@lukaperkov.net \
    --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