All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] uncompressing two gziped images
Date: Wed, 11 Dec 2002 23:50:11 +0100	[thread overview]
Message-ID: <20021211225016.8A943C613A@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 12 Dec 2002 07:53:13 +1300." <8D7C5F56B409554D9D46AC22195807F3061BCA@exchwenz01.dmcwave.co.nz>

In message <8D7C5F56B409554D9D46AC22195807F3061BCA@exchwenz01.dmcwave.co.nz> you wrote:
> 
> My question is how can I uncompress two stand alone images before starting
> one of them (the first one)?

Currently there is no command available to do  this.  Actually,  ther
eis  very  little  support for the handling of the misc image types -
the only thing which is really supported is  what's  needed  to  boot
Linux with or without ramdisk images.

For example, you can use autoscr to execute the contents of a  script
images - but it will not handle a compressed script image (yet).

So all you can do is implement the required features,  and  send  the
patches.

> Before I start changing the code to do this for us I though I'd ask incase
> there is a way I have not been able to figure out yet.  I have tried using
> mkimage and setting one to a Linux kernel image and the other one to a RAM
> disk but the RAM disk is not decompressed before being relocated.  

No, this won;t work. You have to add new code.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
"You shouldn't make my toaster angry." - Household security explained
in "Johnny Quest"

      reply	other threads:[~2002-12-11 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 18:53 [U-Boot-Users] uncompressing two gziped images Rod Boyce
2002-12-11 22:50 ` Wolfgang Denk [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=20021211225016.8A943C613A@atlas.denx.de \
    --to=wd@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 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.