From: Robert Schwebel <robert@schwebel.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] booting linux kernel problem...
Date: Fri, 21 Feb 2003 21:31:34 +0100 [thread overview]
Message-ID: <20030221203134.GC18249@pengutronix.de> (raw)
In-Reply-To: <430C2158-442C-11D7-B791-00039390D626@pepper.com>
On Wed, Feb 19, 2003 at 12:04:52PM -0500, Michael Frey wrote:
> Anyone have any ideas why this might be. I went through the steps of
> creating a gzipped linux image and creating a uboot image using mkimage
> than building an srecord image.
Try my PXA patch (on our web site) for the Linux kernel - it lets you
'make uImage UBOOT=/where/u-boot/lives' to make an uImage.
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Braunschweiger Str. 79, 31134 Hildesheim, Germany
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4
prev parent reply other threads:[~2003-02-21 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 17:04 [U-Boot-Users] booting linux kernel problem Michael Frey
2003-02-19 20:14 ` Wolfgang Denk
2003-02-19 20:16 ` Kyle Harris
2003-02-19 20:27 ` Michael Frey
2003-02-19 22:52 ` Geir Thomassen
2003-02-19 23:22 ` Kyle Harris
2003-02-21 20:31 ` Robert Schwebel [this message]
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=20030221203134.GC18249@pengutronix.de \
--to=robert@schwebel.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