All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Steven Scholz <steven.scholz@imc-berlin.de>,
	LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: BOOT_TARGET pImage & uImage ???
Date: Thu, 18 Sep 2003 20:26:54 +0200	[thread overview]
Message-ID: <20030918182654.GA1444@mars.ravnborg.org> (raw)
In-Reply-To: <20030918180834.GC6692@ip68-0-152-218.tc.ph.cox.net>


> What I want is three things:
> 1) The 'mkimage' target must be done in such a fashion that it will
> never run into a 'cannot execute' problem.  My suggestion is to have the
> Makefile do a:
> @chmod +x mkimage.sh
> Or so.  In 2.5/2.6, the build system will handle this for you,
> automagically, on .sh files I believe.  For 2.4, you must handle this
> explicitly.

In 2.6 you need to locate the script in scripts/ and add it to the
makefile to make this happen. Do not do that.

Best way IMO is to use:
$(CONFIG_SHELL) mkimage.sh

This works in both 2.4 and 2.6.

> 2) Do we really need 'pImage' and 'uImage' or can we just have 'uImage'

Please kill pImage. PPCBOOT is dead, we shall focus on "Das U-boot".

	Sam

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2003-09-18 18:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15 10:16 BOOT_TARGET pImage & uImage ??? Steven Scholz
2003-09-15 15:09 ` Tom Rini
2003-09-18 11:09   ` Steven Scholz
2003-09-18 13:52     ` Brian Waite
2003-09-18 18:31       ` Tom Rini
2003-09-18 18:08     ` Tom Rini
2003-09-18 18:22       ` Brian Waite
2003-09-18 18:28         ` Tom Rini
2003-09-18 18:40         ` Wolfgang Denk
2003-09-18 18:26       ` Sam Ravnborg [this message]
2003-09-18 18:33         ` Tom Rini
2003-09-18 19:38           ` Sam Ravnborg
2003-09-18 20:07             ` 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=20030918182654.GA1444@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=steven.scholz@imc-berlin.de \
    --cc=trini@kernel.crashing.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.