public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] bin_dep.sh Support
Date: Mon, 06 Apr 2009 11:39:56 +0200	[thread overview]
Message-ID: <m2ocva86j7.fsf@ohwell.denx.de> (raw)
In-Reply-To: <20090403175432.3223A83797DC@gemini.denx.de> (Wolfgang Denk's message of "Fri, 03 Apr 2009 19:54:32 +0200")

Hi,

> Dear Prafulla Wadaskar,
>
> In message <1238759359-6544-2-git-send-email-prafulla@marvell.com> you wrote:
>> From: prafulla_wadaskar <prafulla@marvell.com>
>> 
>> In some cases the u-boot.bin need to be processed further
>> to create bootable u-boot binary from boot device
>> This processing may be cpu,soc and/or board spcific
>> bin_dep.sh provides a mechanism to execute bin_dep.sh
>> if present in above platform specific folders
>> 
>> Signed-off-by: prafulla_wadaskar <prafulla@marvell.com>
>> ---
>>  Makefile         |    2 +
>>  tools/bin_dep.sh |   79 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>  2 files changed, 81 insertions(+), 0 deletions(-)
>>  create mode 100755 tools/bin_dep.sh
>
> I don't see use cases for this.  This should probably remain out of
> tree.

If the wrapping is needed to get a working U-Boot image for this
specific board, I'll vote to add the code.

On the other hand, I wouldn't probably add this to the u-boot.bin
target.  A makefile should really specify what file is generated from
what and generating an extra target in the u-boot.bin rule somewhat
violates this rule.

I'd say, add another target and the script.  Hopefully we can make this
as generic as possible so that other boards needing this can only plug
in their script.

Cheers
  Detlev

-- 
I will use free software even if it is less powerful, or less reliable,
because freedom is the most important thing, and that is what the Free
Software movement is about.  How we get freedom.
                       -- Richard M. Stallman
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

  parent reply	other threads:[~2009-04-06  9:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 11:49 [U-Boot] [PATCH] debug_print macros support Prafulla Wadaskar
2009-04-03 11:49 ` [U-Boot] [PATCH] bin_dep.sh Support Prafulla Wadaskar
2009-04-03 11:49   ` [U-Boot] [PATCH] Macronix MX25xx MTD SPI flash driver Prafulla Wadaskar
2009-04-03 14:14     ` Mike Frysinger
2009-04-06  7:23       ` Prafulla Wadaskar
2009-04-06  7:39         ` Mike Frysinger
2009-04-06  8:27           ` Prafulla Wadaskar
2009-04-06  8:49             ` Mike Frysinger
2009-04-03 17:54   ` [U-Boot] [PATCH] bin_dep.sh Support Wolfgang Denk
2009-04-06  7:34     ` Prafulla Wadaskar
2009-04-06  8:05       ` Wolfgang Denk
2009-04-06  8:13         ` Ronen Shitrit
2009-04-06  8:24           ` Wolfgang Denk
2009-04-06  8:36             ` Ronen Shitrit
2009-04-06  9:11               ` Wolfgang Denk
2009-04-06  9:03             ` Mike Frysinger
2009-04-06  9:16               ` Wolfgang Denk
2009-04-06  9:33                 ` Mike Frysinger
2009-04-06 10:28                   ` Wolfgang Denk
2009-04-06 10:49                     ` Mike Frysinger
2009-04-06  9:38                 ` Prafulla Wadaskar
2009-04-06 10:16                   ` Mike Frysinger
2009-04-06 11:00                   ` Wolfgang Denk
2009-05-26  9:08                   ` Stefan Roese
2009-04-06 19:30             ` Scott Wood
2009-04-06 19:49               ` Wolfgang Denk
2009-04-06 23:01                 ` Mike Frysinger
2009-04-06  9:39     ` Detlev Zundel [this message]
2009-04-06  9:43       ` Prafulla Wadaskar
2009-04-03 17:53 ` [U-Boot] [PATCH] debug_print macros support Wolfgang Denk
2009-04-06  5:32   ` Prafulla Wadaskar
2009-04-06  6:31     ` Mike Frysinger
2009-04-06  6:43       ` Prafulla Wadaskar
2009-04-06  7:56     ` Wolfgang Denk
2009-04-06  8:05       ` Mike Frysinger

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=m2ocva86j7.fsf@ohwell.denx.de \
    --to=dzu@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