From: "xuxian" <lsfdxuxian@gmail.com>
To: 'Matthew Percival' <matthew@capgo.com>,
'Linux OMAP Open Source' <linux-omap-open-source@linux.omap.com>
Subject: RE: problems on building root filesystem using scratchbox and meamo
Date: Fri, 9 Dec 2005 10:54:41 +0800 [thread overview]
Message-ID: <4398f1fe.19db014d.48d8.ffffdf58@mx.gmail.com> (raw)
In-Reply-To: <1133993121.8897.4.camel@localhost.localdomain>
Hi,
What part decides the size of erase block? The hardware, the kernel or the
root filesystem?
Best regards,
xuxian
-----Original Message-----
From: linux-omap-open-source-bounces@linux.omap.com
[mailto:linux-omap-open-source-bounces@linux.omap.com] On Behalf Of Matthew
Percival
Sent: Thursday, December 08, 2005 6:05 AM
To: Linux OMAP Open Source
Subject: RE: problems on building root filesystem using scratchbox and meamo
G'Day,
> I use the command:
> mkfs.jffs2 -p -l -e 0x20000 -n -v -r /home/xuxian/rootfs/fs -o
> filesys.jffs2
> to make the root filesystem image.
For my OSK, -e 0x20000 is the correct size; the command I use is
basically the same as you.
> What size of the erase block will be fine? I can't access the file
/proc/mtd
> because I cannot mount the filesystem. Does the kernel determine the size
of
> erase block or anything else? Where can I set the erase block size?
If you mount your filesystem as an NFS root rather than an image,
then
you can read /proc/mtd, but I would say you are most likely correct in
your erase size.
I am not familiar with scratchbox or maemo, so it is possible your
problem relates to them, but I cannot be sure. Sorry, I probably will
not be of much help here.
-- Matthew
_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
next prev parent reply other threads:[~2005-12-09 2:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 13:37 problems on building root filesystem using scratchbox and meamo xuxian
2005-12-05 22:11 ` Matthew Percival
2005-12-07 6:14 ` xuxian
2005-12-07 22:05 ` Matthew Percival
2005-12-09 2:54 ` xuxian [this message]
2005-12-09 3:45 ` Menon, Nishanth
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=4398f1fe.19db014d.48d8.ffffdf58@mx.gmail.com \
--to=lsfdxuxian@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=matthew@capgo.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 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.