All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] Add ubi volume image support, fix ubifs
Date: Thu, 12 Feb 2009 23:45:47 +0100	[thread overview]
Message-ID: <gn28qr$aac$1@ger.gmane.org> (raw)
In-Reply-To: <20090210204817.GH11815@smtp.west.cox.net>

On 10-02-09 21:48, Tom Rini wrote:
> Hey all.  I'd like to commit the following patch.  This will add support
> for generating single image UBI volumes as well as fix creating ubifs
> images.  Going backwards here, the problem with ubifs images right now
> is that you must pass in -m -e -c -r and -o args in order to get an
> image to come out and only -r / -o are not flash part specific.  To fix
> this, on ubifs images, pass in ${MKUBIFS_ARGS}.  Why not just
> ${EXTRA_IMAGECMD} ? That's because making a UBI volume requires a
> different set of mandatory arguments too.  And as there's no way (today)
> to have IMAGETYPE=foo require IMAGETYPE=bar to be built previously, we
> need to use a separate mechanism here (similar to ext2/3 and blocksize).
> To pass in the ubinize args we then go and set UBINIZE_ARGS and then we
> get our 1 image UBI volume to come out if mtd-utils-native=1.2.0+git is
> being used.
>
> As an example, on a board we have with a Samsung K9F2G08U0M we do:
> # Make 256MiB/128KiB
> MKUBIFS_ARGS = "-m 2048 -e 126976 -c 2047"
> UBINIZE_ARGS = "-m 2048 -p 128KiB -s 512"

To get the values for these params:

http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=76af265d0f1a9ed377dbaba7be03fe23643910fe

# do ubiattach /dev/ubi_ctrl -m 4
# From dmesg:
# UBI: smallest flash I/O unit:    2048
# UBI: logical eraseblock size:    129024 bytes
# from ubiattach stdout:
# UBI device number 0, total 1996 LEBs
MKUBIFS_ARGS = "-m 2048 -e 129024 -c 1996"

# do ubiattach /dev/ubi_ctrl -m 4
# from dmesg:
# UBI: smallest flash I/O unit:    2048
# UBI: physical eraseblock size:   131072 bytes (128 KiB)
# UBI: sub-page size:              512
UBINIZE_ARGS = "-m 2048 -p 128KiB -s 512"

regards,

Koen




      parent reply	other threads:[~2009-02-12 22:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 20:48 [RFC] Add ubi volume image support, fix ubifs Tom Rini
2009-02-10 22:43 ` Koen Kooi
2009-02-10 22:59   ` Tom Rini
2009-02-10 23:42     ` Koen Kooi
2009-02-11  0:27       ` Tom Rini
2009-02-11  8:09         ` Koen Kooi
2009-02-11 16:18         ` John Willis
2009-02-12 22:45 ` Koen Kooi [this message]

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='gn28qr$aac$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.