public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Squashfs
Date: Thu, 02 Mar 2006 10:54:53 -0600	[thread overview]
Message-ID: <4407235D.3060601@orkun.us> (raw)
In-Reply-To: <20060301.anF.55534500@192.168.0.1>

Brian Johnson wrote:
> Just getting started with this stuff so I hope I don't ask too many newbie
> questions
> 
> I've read that squashfs is supposed to be an improvement over cramfs but I
> couldn't find any info about squashfs in the terrific U-Boot info at
> http://www.denx.de/wiki/view/DULG
> 
> Is it basically the same setup as for a cramfs root?
> 
> How would it rank in the table shown at
> http://www.denx.de/wiki/view/DULG/RootFileSystemSelection ?

We use UImage based on squashfs (gzip) in our UImage. U-Boot does not 
care what type of file system is in UImage formatted file. It only cares 
the file is a proper UImage. If you are looking at any U-Boot commands 
to deal with files inside the squashfs image U-Boot does not provide any 
such support.

Why don't you try generating cramfs and squashfs etc. based UImage files 
using your root file system contents and compare. Here is some date for 
you based on our PPC405PR based system which may or might not be 
representative.

RAM Memory After Boot:
fs_type available used free
ext2  30724 17636 13088
cramfs  30724 9700 21024
squashfs  30724 9800 20924

File System Size:
fs_type uncompessed gzip bzip2
ext2  11564032 3183668 2922595
cramfs  3805184 3783755 3736662
squashfs  3203072 3182423 3157283

Best regards,
Tolunay

      parent reply	other threads:[~2006-03-02 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-01 15:33 [U-Boot-Users] Squashfs Brian Johnson
2006-03-01 16:07 ` Wolfgang Denk
2006-03-02 16:54 ` Tolunay Orkun [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=4407235D.3060601@orkun.us \
    --to=listmember@orkun.us \
    --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