linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo70@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: UBI, no sub-pages support
Date: Tue, 19 Aug 2014 13:28:25 +0200	[thread overview]
Message-ID: <53F334D9.5030902@gmail.com> (raw)

Dear all,

i am running UBI/UBIFS on a TI AM1808 / OPAM-L cpu, MT29F1G08 NAND and
kernel 3.5.1.

MT29F1G08 has 128KB pages, and 2048B PEB's.

After first attempt to create UBI/UBIFS image using 512B sub-pages, i
had several UBI errors, so i realized sub-pages are not supported in the
OMAP-L driver at this kernel version (seems to start to be supported
form 3.10.x).

So i prepare the image from buildroot without subpage now, with these
settings:

      [ ] jffs2 root filesystem
      [*] ubifs root filesystem
      (0x1f000) UBI logical erase block size
      (0x800) UBI minimum I/O size
      (1024) Maximum LEB count
         ubifs runtime compression (gzip)  --->
         Compression method (no compression)  --->
      [*]   Embed into an UBI image
      (0x20000) UBI physical erase block size
      (0)     UBI sub-page size

buildroot/output/host/usr/sbin/mkfs.ubifs --space-fixup -d
buildroot/output/target -e 0x1f000 -c 1024 -m 0x800 -x zlib -o
buildroot/output/images/rootfs.ubifs


buildroot/output/host/usr/sbin/ubinize -o
buildroot/output/images/rootfs.ubi -m 0x800 -p 0x20000 ubinize.cfg

I executed both mtd-utils "runtest.sh" and integck, and had no issues.
Could you maybe confirm this settings are correct and i am not going
trough issues using the fs ?

Another question is: is there a UBI performance loss using pages as
minimal I/O (no subpages) or i can consider it insignificant ?

Many Thanks
Angelo Dureghello

             reply	other threads:[~2014-08-19 11:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 11:28 Angelo Dureghello [this message]
2014-09-08 10:03 ` UBI, no sub-pages support Artem Bityutskiy

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=53F334D9.5030902@gmail.com \
    --to=angelo70@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).