From: Artem Bityutskiy <dedekind@infradead.org>
To: Thang Dao Duy <hanbaoquansexy@gmail.com>
Cc: manoj23@gmail.com, linux-mtd@lists.infradead.org
Subject: Re: jffs2 on ubi volume
Date: Fri, 26 Jun 2009 09:32:13 +0300 [thread overview]
Message-ID: <1245997933.9487.64.camel@localhost.localdomain> (raw)
In-Reply-To: <a1fb7300906252320k655298dcg33f56ca702736ac@mail.gmail.com>
On Fri, 2009-06-26 at 13:20 +0700, Thang Dao Duy wrote:
> manoj23@gmail.com wrote:
>
> >Answering my own question, I got it to work by creating a /dev/ubi0_1
> >device file and then using ubiupdatevol.
>
> >>./ubimkvol /dev/ubi0 -s25MiB -Nubivol1 -n1
> >> mknod /dev/ubi0_1 c 253 2
> >> ./ubiupdatevol /dev/ubi0_1 sum.jffs2.rootfs
> >> mkdir /tmp/flash
>
>
> Command ubimkvol will create a device /dev/ubi0_1, so "mknod
> /dev/ubi0_1 c 253 2" may be unnecessary.
No, not really. Udev will do this, not ubimkvol. And if you do not
have udev, the device node will not be created. But may be it would
be a good idea to teach ubimkvol doing this.
> manoj23@gmail.com wrote:
>
> >> mount -t jffs2 /dev/mtdb-nvdata /tmp/flash
>
> jffs2 file system does not work on UBI API, it works on MTD API. so we
> cannot mount jffs2 on ubi volume. We can use ubifs on ubi volume:
>
> mount -t ubifs ubi0_1 /mnt/
Right, but you still may use jffs2 with ubi. We have the gluebi emulator
for this:
http://www.linux-mtd.infradead.org/faq/ubi.html#L_run_jffs2
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-06-26 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 6:20 jffs2 on ubi volume Thang Dao Duy
2009-06-26 6:32 ` Artem Bityutskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-23 2:18 Manoj
2009-06-24 0:46 ` Manoj
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=1245997933.9487.64.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=hanbaoquansexy@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=manoj23@gmail.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