From: "well" <well@zinwell.com.tw>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: can jffs2 on DOC?
Date: Thu, 25 Jul 2002 17:06:39 +0800 [thread overview]
Message-ID: <003b01c233ba$961fdf40$8600a8c0@well> (raw)
Hi
I searched and read all the list but still confusing...
I'm sure my DOC is OK with cat /proc/mtd, but I just can't mount jffs2 image
on DOC
dev: size erasesize name
mtd0: 01000000 00004000 "DiskOnChip 2000"
My step to mount jffs2 is:
mkfs.jffs2 -r /imgdata -o /data.img -e 0x4000
dd if=/data.img of=/dev/mtd0
mount -t jffs2 /dev/mtdblock0 /mnt
and my system hangs.......
These are the questions:
1) Can I mount jffs2 image on DOC?
2) To support jffs2, what kernel MTD options should I enable, I'm not sure
my choice is right?
Any response is appreciate...
W.B.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-07-25 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 9:06 well [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-25 15:32 can jffs2 on DOC? Jean-Denis Boyer
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='003b01c233ba$961fdf40$8600a8c0@well' \
--to=well@zinwell.com.tw \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).