From: Saurabh Jain <saurabh@thinvent.in>
To: linux-mtd@lists.infradead.org
Subject: Squashfs over UBI
Date: Mon, 25 Jan 2010 00:46:00 +0530 [thread overview]
Message-ID: <c11c61211001241116i50063d7ds6e2fb4edcce0769@mail.gmail.com> (raw)
Hi!
I've been trying to get squashfs working on a new board with NAND
flash. However, the mtd of the mtdblock I am using contains bad
blocks. When I dd in the squashfs file system, the kernel throws
end_request, nand_erase_nand and mtdblock errors.
I therefore decided to use squashfs over UBI. I saw this discussed in
a couple of places on the web. However, the /dev/ubi0 device created
by ubiattach is a character device. I can't just dd my squashfs into
it. If I create a UBIFS over this /dev/ubi0, and then put my squashfs
into it, that works, but now I've got "double compression", something
I don't want on an embedded system.
Is it possible to get squashfs to use the bad block avoidance features
of UBI, without using UBIFS?
Regards,
Saurabh
http://www.thinvent.in
next reply other threads:[~2010-01-24 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 19:16 Saurabh Jain [this message]
2010-02-03 16:17 ` Squashfs over UBI 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=c11c61211001241116i50063d7ds6e2fb4edcce0769@mail.gmail.com \
--to=saurabh@thinvent.in \
--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