From: Brian Waite <waite@skycomputers•com>
To: Tom Rini <trini@kernel•crashing.org>,
Steven Scholz <steven.scholz@imc-berlin•de>
Cc: LinuxPPC <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: BOOT_TARGET pImage & uImage ???
Date: Thu, 18 Sep 2003 14:22:28 -0400 [thread overview]
Message-ID: <200309181422.32546.waite@skycomputers.com> (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.
Altough messy, I make this happen in the patch I supply. I can change it to do
the straight chmod in the scrip[ts directory if that is cleaner.
> 2) Do we really need 'pImage' and 'uImage' or can we just have 'uImage'
> ?
I think uImage is enough. Wolfgang strongly discourages any use of PPCBoot
these days and it just seems silly.
> 3) I really (really!) want a patch for 2.4 and 2.5/2.6 at the same time.
This was one of the reasons for not supplying the patch previously.
I will try to pull together a 2.5/2.6 patch but I have not worked under
2.5/2.6 at all. When I initially did the 2.4 patch I pulled the 2.5 tree but
I didn't have time to understand the layout. Also, unless someone has a board
that will boot a uImage target I can only supply an untested patch. I'll take
some time and see if I can pull something I am comfortable with in the next
few days. Is there anyone who could help with testing?
Thanks
Brian
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-18 18:22 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 [this message]
2003-09-18 18:28 ` Tom Rini
2003-09-18 18:40 ` Wolfgang Denk
2003-09-18 18:26 ` Sam Ravnborg
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=200309181422.32546.waite@skycomputers.com \
--to=waite@skycomputers$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=steven.scholz@imc-berlin$(echo .)de \
--cc=trini@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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