From: Hamish Moffatt <hamish@cloud.net.au>
To: dedekind@infradead.org, linux-mtd@lists.infradead.org
Subject: ubiupdatevol from pipe/compressed file
Date: Mon, 19 May 2008 18:47:46 +1000 [thread overview]
Message-ID: <20080519084746.GA19325@cloud.net.au> (raw)
Hi,
We discussed this briefly a few months back but I want to investigate a
bit further.
I would like to be able to update a ubi volume from a compressed file.
My system has limited RAM so I can't always keep the whole file
uncompressed in RAM, and I'd prefer not to uncompress it to temporary
space on flash, just to copy it somewhere else.
I'm doing this on a block device with "zcat img.gz | dd of=..." but
ubiupdatevol doesn't accept a pipe.
Reading the source this looks quite difficult to fix - it really must
know how many bytes are to be programmed in advance because it
communicates that to the kernel.
One solution I see is to add decompression support directly into
ubiupdatevol. eg with zlib it can gzseek() to the end of the file to get
the length, then rewind. I modified flashcp once to do this. However I
prefer to use better compression (lzma or bzip2) and we don't want to
add all of these to mtd-utils I think.
Alternatively allow the uncompressed file size to be specified as a
ubiupdatevol parameter. In my application I can store the uncompressed
file size and provide it to ubiupdatevol ok.
Artem, do you have any other ideas?
Thanks
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next reply other threads:[~2008-05-19 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 8:47 Hamish Moffatt [this message]
2008-05-19 8:54 ` ubiupdatevol from pipe/compressed file Artem Bityutskiy
2008-05-20 8:39 ` Hamish Moffatt
2008-05-20 11:19 ` Artem Bityutskiy
2008-05-20 11:53 ` Artem Bityutskiy
2008-06-27 14:36 ` Artem Bityutskiy
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=20080519084746.GA19325@cloud.net.au \
--to=hamish@cloud.net.au \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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