All of lore.kernel.org
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] gunzip command?
Date: 26 Sep 2003 15:01:47 +0200	[thread overview]
Message-ID: <873cejhfes.fsf@deepthought.outer.space.org> (raw)
In-Reply-To: <3F742B84.7040007@imc-berlin.de>

Hi Steven,

> on my board U-Boot should program an FPGA before booting linux. Unfortunatly the
> file is quite big (>160KB). So I store a gzipped version of it in my flash.
> Actually I stored an image created with mkimage
> 
> DAB4K2> imi 40040000
> 
> ## Checking Image at 40040000 ...
>     Image Name:   DAB4K_TEST-
>     Created:      2003-09-22   8:20:19 UTC
>     Image Type:   PowerPC U-Boot Firmware (gzip compressed)
>     Data Size:    56098 Bytes = 54.8 kB
>     Load Address: 00000000
>     Entry Point:  00000000
>     Verifying Checksum ... OK
> 
> So what I need now is a way to uncompress the data to RAM before I can call
> "fpga load".
> 
> My questions:
> 1. Should we add a "gunzip" command to U-Boot?
> 2. Should we add a command (similar to bootm) that takes an image, decompresses
> it and checks CRC etc.?
> 3. Or should we put this into the "fpga load" command?
> 
> I would go for the first. Maybe the second. Third seems to be too limited.
> 
> Any comments?

Yes, why implement things that are already there?  See our
documentation[1] for exactly this problem.  I know, it takes some
courage to use "bootm" to uncompress, but hey, it works...

Cheers
  Detlev

[1] https://www.denx.de/twiki/bin/view/DULG/HowCanILoadAndUncompressACompressedImage

-- 
"The number you have dialed is imaginary. Please rotate your phone 90
degrees and try again."

  reply	other threads:[~2003-09-26 13:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-26 12:05 [U-Boot-Users] gunzip command? Steven Scholz
2003-09-26 13:01 ` Detlev Zundel [this message]
2003-09-26 13:13   ` Steven Scholz

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=873cejhfes.fsf@deepthought.outer.space.org \
    --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 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.