From: Oren <oren_s3@VERIFONE.com>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubiattach problem
Date: Tue, 7 Jul 2009 16:21:32 +0300 [thread overview]
Message-ID: <1246972892.2208.5.camel@tlvorens3lnx> (raw)
In-Reply-To: <1246971115.20721.308.camel@localhost.localdomain>
ubinize: LEB size: 126976
ubinize: PEB size: 131072
ubinize: min. I/O size: 2048
ubinize: sub-page size: 2048
ubinize: VID offset: 2048
ubinize: data offset: 4096
ubinize: loaded the ini-file "images/ubinize.cfg"
ubinize: count of sections: 1
ubinize: parsing section "ubifs"
ubinize: mode=ubi, keep parsing
ubinize: volume type: dynamic
ubinize: volume ID: 0
ubinize: volume size: 16777216 bytes
ubinize: volume name: NAND-block1
ubinize: volume alignment: 1
ubinize: autoresize flags found
ubinize: adding volume 0
ubinize: writing volume 0
ubinize: image file: images/ubifs_ncomp.img
ubinize: writing layout volume
ubinize: done
On Tue, 2009-07-07 at 15:51 +0300, Artem Bityutskiy wrote:
> On Tue, 2009-07-07 at 15:08 +0300, Oren wrote:
> > mkfs.ubifs/mkfs.ubifs -r ~/BRCMLinux/Linux_2_6_27/mtd-utils/myrfs
> > --compr="none" -m 2048 -e 129024 -c 2047 -o images/ubifs_ncomp.img
> > ubi-utils/ubinize -o images/ubi_ncomp.img -m 2048 -p 128KiB -s 2048
> > images/ubinize.cfg
> >
> >
> > ubinize.cfg:
> >
> > [ubifs]
> > mode=ubi
> > image=images/ubifs_ncomp.img
> > vol_id=0
> > vol_size=16MiB
> > vol_type=dynamic
> > vol_name=rootfs
> > vol_flags=autoresize
> >
>
> Can you add -v to ubinize and see if there is a
> "writing layout volume" print?
>
next prev parent reply other threads:[~2009-07-07 13:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <baa101c9fe67$d7b31f0a$b65b1ec0@verifone.com>
2009-07-07 6:25 ` ubiattach problem Artem Bityutskiy
2009-07-07 10:32 ` Oren
2009-07-07 10:42 ` Artem Bityutskiy
2009-07-07 12:08 ` Oren
2009-07-07 12:51 ` Artem Bityutskiy
2009-07-07 13:21 ` Oren [this message]
2009-07-07 13:28 ` Artem Bityutskiy
2009-07-07 14:08 ` Oren
2009-07-07 14:19 ` Artem Bityutskiy
2009-07-07 14:38 ` Artem Bityutskiy
2009-07-07 14:49 ` Oren
2009-07-07 14:53 ` Artem Bityutskiy
2009-07-07 15:30 ` Oren
2009-07-07 15:38 ` Oren
2009-07-07 15:45 ` Artem Bityutskiy
2009-07-12 7:19 ` Oren Sokolowsky
2009-07-12 14:06 ` Artem Bityutskiy
2009-07-27 12:54 ` Oren
2009-08-09 4:36 ` Artem Bityutskiy
2009-07-06 13:50 Oren
2009-07-06 14:05 ` Artem Bityutskiy
2011-09-09 9:53 ` marco
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=1246972892.2208.5.camel@tlvorens3lnx \
--to=oren_s3@verifone.com \
--cc=dedekind@infradead.org \
--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