From: Josh Boyer <jwboyer@gmail.com>
To: "Adams Richard-W36112" <rgadams@motorola.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: problem with 2k page NAND with squashfs
Date: Tue, 22 Jan 2008 08:49:10 -0600 [thread overview]
Message-ID: <20080122084910.2939d94a@weaponx> (raw)
In-Reply-To: <A2EC06CB0E393B4C8EB220B286B7083E05897213@ct11exm60.ds.mot.com>
On Tue, 22 Jan 2008 09:15:29 -0500
"Adams Richard-W36112" <rgadams@motorola.com> wrote:
> I have an arm-based embedded system running a 2.6.10 kernel. I'm using
> a squashfs file system (read only) on the Flash device. The system was
> working fine with a 512 byte page Flash part. I started having problems
> when I upgraded to a 2048 byte page Flash part. When I mount the squash
> file system, it can successfully find the super block, but squashfs
> fails (unable to read inode [5ff3:120]) when it try's to finish the
> mount. My suspicions are that with the older kernel (2.6.10) it may not
> fully support the larger page devices. Is there an achieve of patches
> that are applicable for a 2.6.10 kernel? I tried to look through the
> mailing list archive, but without a search tool and not knowing what
> month I'm looking for the task became tedious.
http://linux-mtd.infradead.org/source.html#kernelversions
2.6.10 pre-dates git even, so you are likely stuck doing diffs from
kernel tarballs.
josh
next prev parent reply other threads:[~2008-01-22 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 14:15 problem with 2k page NAND with squashfs Adams Richard-W36112
2008-01-22 14:49 ` Josh Boyer [this message]
2008-01-22 14:57 ` Adams Richard-W36112
2008-01-23 9:27 ` Ricard Wanderlof
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=20080122084910.2939d94a@weaponx \
--to=jwboyer@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rgadams@motorola.com \
/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