This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: JFFS2 questions with eCos
- From: "Steven_cheng" <05071 at alphanetworks dot com>
- To: "Andrew Lunn" <andrew at lunn dot ch>
- Cc: <ecos-discuss at sources dot redhat dot com>
- Date: Mon, 3 Oct 2005 17:35:01 +0800
- Subject: Re: [ECOS] JFFS2 questions with eCos
- References: <20050920111517.GH24142@lunn.ch> <003101c5bdd8$36bd7a20$01473264@stevencheng> <20050920120119.GI24142@lunn.ch> <000c01c5be6f$fa317640$01473264@stevencheng> <20050921064747.GC28077@lunn.ch> <007401c5c4aa$37820740$01473264@stevencheng> <20050929072241.GY28077@lunn.ch> <009201c5c4da$f8dc50f0$01473264@stevencheng> <20050929105609.GZ28077@lunn.ch> <005601c5c7f2$9823e730$01473264@stevencheng> <20051003083425.GC28077@lunn.ch>
Hi Andrew,
I'm sorry to disturb you, because I take some tests
with the mkfs.jffs2.
When I use the following commands, the size of the image are
different, it is tested in i386-linux and cygwin.
(1) ./mkfs.jffs2 -b -o myjffs2_1.img -r
jffs2_dir/ --pad=4194304 --eraseblock=131072
[image size = 4,194,304 bytes ]
(2) ./mkfs.jffs2 -b -o myjffs2_2.img -r jffs2_dir/ --pad=4194304 -e 131072
[image size = 4,194,304 bytes ]
(3) ./mkfs.jffs2 -b -o myjffs2_3.img -r jffs2_dir/ --pad=4194304 -e=131072
[ error !!
i386linux: Increasing erase size to 8KiB minimum
cygwin: mkfs.jffs2: Unrecognisable erase size]
(4) ./mkfs.jffs2 -b -o myjffs2_4.img -r jffs2_dir/ -p 4194304 -e 131072
[image size = 393,216 bytes]
(5) ./mkfs.jffs2 -b -o myjffs2_5.img -r jffs2_dir/ -p=4194304 -e 131072
[image size = 320,688 bytes]
So I am not sure which is the correct usage !!
Thank yor for your reply ~~
Steven Cheng
----- Original Message -----
From: "Andrew Lunn" <andrew@lunn.ch>
To: "Steven_cheng" <05071@alphanetworks.com>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Monday, October 03, 2005 4:34 PM
Subject: Re: [ECOS] JFFS2 questions with eCos
> On Mon, Oct 03, 2005 at 04:15:19PM +0800, Steven_cheng wrote:
> > Hi Adnrew,
> >
> > Thank you for your reply!!
> > But I still have some questions about mkfs.jffs2.
>
> There is a man page you know....
>
> >
> > Q1 : Can you tell me what is the different betweem -e
> > and --eraseblock=size,
>
> None. One is a short opt and one is a long opt. Standard GNU practice.
>
> > -p and --pad=size ??
>
> None, although there was/is a bug which i think means one does not
> work. Check the actuall size of the image created.
>
> > Q2 : "ereaseblock=size" and "--pad=size" in the statements, the unit is
> > bytes or Kbytes ??
>
> Why not read the man page and save us all waisted time...
>
> Options that take SIZE arguments can be specified as either
decimal
> (e.g., 65536), octal (0200000), or hexidecimal (0x1000).
>
>
> > I can't understand the meaning of the help as following:
> >
> > -p, --pad[=SIZE] Pad output to SIZE bytes with 0xFF. If SIZE is
> > not specified, the output is padded to the end
of
> > the final erase block.
> >
> > -e, --eraseblock=SIZE Use erase block size SIZE (default: 64KiB)
>
> What don't use understand?
>
> Andrew
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss